Devices, methods and systems for visual imaging arrays

ABSTRACT

Computationally implemented methods and systems include acquiring a request for particular image data that is part of a scene, transmitting the request for the particular image data to an image sensor array that includes more than one image sensor and that is configured to capture the scene that is larger than the requested particular image data, receiving only the particular image data from the image sensor array, and transmitting the received particular image data to at least one requestor. In addition to the foregoing, other aspects are described in the claims, drawings, and text.

CROSS-REFERENCE TO RELATED APPLICATIONS

If an Application Data Sheet (ADS) has been filed on the filing date ofthis application, it is incorporated by reference herein. Anyapplications claimed on the ADS for priority under 35 U.S.C. §§119, 120,121, or 365(c), and any and all parent, grandparent, great-grandparent,etc. applications of such applications, are also incorporated byreference, including any priority claims made in those applications andany material incorporated by reference, to the extent such subjectmatter is not inconsistent herewith.

The present application is related to and/or claims the benefit of theearliest available effective filing date(s) from the following listedapplication(s) (the “Priority Applications”), if any, listed below(e.g., claims earliest available priority dates for other thanprovisional patent applications or claims benefits under 35 USC §119(e)for provisional patent applications, for any and all parent,grandparent, great-grandparent, etc. applications of the PriorityApplication(s)). In addition, the present application is related to the“Related Applications,” if any, listed below.

PRIORITY APPLICATIONS

For purposes of the USPTO extra-statutory requirements, the presentapplication claims benefit of priority of U.S. Provisional PatentApplication No. 62/081,559 titled DEVICES, METHODS, AND SYSTEMS FORINTEGRATING MULTIPLE USER VIDEO IMAGING ARRAY, filed 18 Nov. 2014, whichwas filed within the twelve months preceding the filing date of thepresent application or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication claims benefit of priority of U.S. Provisional PatentApplication No. 62/081,560 titled DEVICES, METHODS, AND SYSTEMS FORIMPLEMENTATION OF MULTIPLE USER VIDEO IMAGING ARRAY (MUVIA), filed 18Nov. 2014, which was filed within the twelve months preceding the filingdate of the present application or is an application of which acurrently co-pending application is entitled to the benefit of thefiling date.

For purposes of the USPTO extra-statutory requirements, the presentapplication claims benefit of priority of U.S. Provisional PatentApplication No. 62/082,001 titled DEVICES, METHODS, AND SYSTEMS FORINTEGRATING MULTIPLE USER ACCESS CAMERA ARRAY, filed 19 Nov. 2014 whichwas filed within the twelve months preceding the filing date of thepresent application or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication claims benefit of priority of U.S. Provisional PatentApplication No. 62/082,002 titled DEVICES, METHODS, AND SYSTEMS FORINTEGRATING MULTIPLE USER VIDEO IMAGING ARRAY, filed 19 Nov. 2014, whichwas filed within the twelve months preceding the filing date of thepresent application or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication claims benefit of priority of U.S. Provisional PatentApplication No. 62/156,162 titled DEVICES, METHODS, AND SYSTEMS FORINTEGRATING MULTIPLE USER VIDEO IMAGING ARRAY, filed 1 May 2015 whichwas filed within the twelve months preceding the filing date of thepresent application or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 14/714,239, entitled DEVICES, METHODS AND SYSTEMSFOR VISUAL IMAGING ARRAYS, filed 15 May 2015 with attorney docket no.1114-003-001-000000, which is currently co-pending or is an applicationof which a currently co-pending application is entitled to the benefitof the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication claims benefit of priority of U.S. Provisional PatentApplication No. 62/180,040 titled DEVICES, METHODS, AND SYSTEMS FORINTEGRATING MULTIPLE USER ACCESS CAMERA ARRAY, filed 15 Jun. 2015 whichwas filed within the twelve months preceding the filing date of thepresent application or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 14/791,160, entitled DEVICES, METHODS, AND SYSTEMSFOR VISUAL IMAGING ARRAYS, filed 2 Jul. 2015 with attorney docket no.1114-003-006-000000, which is currently co-pending or is an applicationof which a currently co-pending application is entitled to the benefitof the filing date, and which is a continuation of U.S. patentapplication Ser. No. 14/791,127, entitled DEVICES, METHODS, AND SYSTEMSFOR VISUAL IMAGING ARRAYS filed 2 Jul. 2015 with attorney docket no.1114-003-002-000000.

RELATED APPLICATIONS

None.

The United States Patent Office (USPTO) has published a notice to theeffect that the USPTO's computer programs require that patent applicantsreference both a serial number and indicate whether an application is acontinuation, continuation-in-part, or divisional of a parentapplication. Stephen G. Kunin, Benefit of Prior-Filed Application, USPTOOfficial Gazette Mar. 18, 2003. The USPTO further has provided forms forthe Application Data Sheet which allow automatic loading ofbibliographic data but which require identification of each applicationas a continuation, continuation-in-part, or divisional of a parentapplication. The present Applicant Entity (hereinafter “Applicant”) hasprovided above a specific reference to the application(s) from whichpriority is being claimed as recited by statute. Applicant understandsthat the statute is unambiguous in its specific reference language anddoes not require either a serial number or any characterization, such as“continuation” or “continuation-in-part,” for claiming priority to U.S.patent applications. Notwithstanding the foregoing, Applicantunderstands that the USPTO's computer programs have certain data entryrequirements, and hence Applicant has provided designation(s) of arelationship between the present application and its parentapplication(s) as set forth above and in any ADS filed in thisapplication, but expressly points out that such designation(s) are notto be construed in any way as any type of commentary and/or admission asto whether or not the present application contains any new matter inaddition to the matter of its parent application(s).

If the listings of applications provided above are inconsistent with thelistings provided via an ADS, it is the intent of the Applicant to claimpriority to each application that appears in the Priority Applicationssection of the ADS and to each application that appears in the PriorityApplications section of this application.

All subject matter of the Priority Applications and the RelatedApplications and of any and all parent, grandparent, great-grandparent,etc. applications of the Priority Applications and the RelatedApplications, including any priority claims, is incorporated herein byreference to the extent such subject matter is not inconsistentherewith.

BACKGROUND

This application is related to video imaging arrays that may be capableof handling multiple users and which may transmit less data than theycollect.

SUMMARY

In one or more various aspects, a method includes, but is not limitedto, that which is illustrated in the drawings. In addition to theforegoing, other method aspects are described in the claims, drawings,and text forming a part of the disclosure set forth herein.

In one or more various aspects, a method includes, but is not limitedto, acquiring a request for particular image data that is part of ascene, transmitting the request for the particular image data to animage sensor array that includes more than one image sensor and that isconfigured to capture the scene that is larger than the requestedparticular image data, and receiving only the particular image data fromthe image sensor array. In addition to the foregoing, other methodaspects are described in the claims, drawings, and text forming a partof the disclosure set forth herein.

In one or more various aspects, one or more related systems may beimplemented in machines, compositions of matter, or manufactures ofsystems, limited to patentable subject matter under 35 U.S.C. 101. Theone or more related systems may include, but are not limited to,circuitry and/or programming for carrying out the herein-referencedmethod aspects. The circuitry and/or programming may be virtually anycombination of hardware, software, and/or firmware configured to effectthe herein-referenced method aspects depending upon the design choicesof the system designer, and limited to patentable subject matter under35 USC 101.

In one or more various aspects, a system includes, but is not limitedto, means for acquiring a request for particular image data that is partof a scene, means for transmitting the request for the particular imagedata to an image sensor array that includes more than one image sensorand that is configured to capture the scene that is larger than therequested particular image data, and means for receiving only theparticular image data from the image sensor array. In addition to theforegoing, other system aspects are described in the claims, drawings,and text forming a part of the disclosure set forth herein.

In one or more various aspects, a system includes, but is not limitedto, circuitry for acquiring a request for particular image data that ispart of a scene, circuitry for transmitting the request for theparticular image data to an image sensor array that includes more thanone image sensor and that is configured to capture the scene that islarger than the requested particular image data, and circuitry forreceiving only the particular image data from the image sensor array. Inaddition to the foregoing, other system aspects are described in theclaims, drawings, and text forming a part of the disclosure set forthherein.

In one or more various aspects, a computer program product, comprising asignal bearing medium, bearing one or more instructions including, butnot limited to, one or more instructions for acquiring a request forparticular image data that is part of a scene, one or more instructionsfor transmitting the request for the particular image data to an imagesensor array that includes more than one image sensor and that isconfigured to capture the scene that is larger than the requestedparticular image data, and one or more instructions for receiving onlythe particular image data from the image sensor array. In addition tothe foregoing, other computer program product aspects are described inthe claims, drawings, and text forming a part of the disclosure setforth herein.

In one or more various aspects, a device is defined by a computationallanguage, such that the device comprises one or more interchainedphysical machines ordered for acquiring a request for particular imagedata that is part of a scene, one or more interchained physical machinesordered for transmitting the request for the particular image data to animage sensor array that includes more than one image sensor and that isconfigured to capture the scene that is larger than the requestedparticular image data, and one or more interchained physical machinesordered for receiving only the particular image data from the imagesensor array.

In addition to the foregoing, various other method and/or system and/orprogram product aspects are set forth and described in the teachingssuch as text (e.g., claims and/or detailed description) and/or drawingsof the present disclosure.

The foregoing is a summary and thus may contain simplifications,generalizations, inclusions, and/or omissions of detail; consequently,those skilled in the art will appreciate that the summary isillustrative only and is NOT intended to be in any way limiting. Otheraspects, features, and advantages of the devices and/or processes and/orother subject matter described herein will become apparent by referenceto the detailed description, the corresponding drawings, and/or in theteachings set forth herein.

BRIEF DESCRIPTION OF THE FIGURES

For a more complete understanding of embodiments, reference now is madeto the following descriptions taken in connection with the accompanyingdrawings. The use of the same symbols in different drawings typicallyindicates similar or identical items, unless context dictates otherwise.The illustrative embodiments described in the detailed description,drawings, and claims are not meant to be limiting. Other embodiments maybe utilized, and other changes may be made, without departing from thespirit or scope of the subject matter presented here.

FIG. 1, including FIGS. 1-A through 1-AN, shows a high-level systemdiagram of one or more exemplary environments in which transactions andpotential transactions may be carried out, according to one or moreembodiments. FIG. 1 forms a partially schematic diagram of anenvironment(s) and/or an implementation(s) of technologies describedherein when FIGS. 1-A through 1-AN are stitched together in the mannershown in FIG. 1-D, which is reproduced below in table format.

In accordance with 37 C.F.R. §1.84(h)(2), FIG. 1 shows “a view of alarge machine or device in its entirety . . . broken into partial views. . . extended over several sheets” labeled FIG. 1-A through FIG. 1-AN(Sheets 1-40). The “views on two or more sheets form, in effect, asingle complete view, [and] the views on the several sheets . . . [are]so arranged that the complete figure can be assembled” from “partialviews drawn on separate sheets . . . linked edge to edge. Thus, in FIG.1, the partial view FIGS. 1-A through 1-AN are ordered alphabetically,by increasing in columns from left to right, and increasing in rows topto bottom, as shown in the following table:

TABLE 1 Table showing alignment of enclosed drawings to form partialschematic of one or more environments. Pos. (0, 0) X-Pos 1 X-Pos 2 X-Pos3 X-Pos 4 X-Pos 5 X-Pos 6 X-Pos 7 X-Pos 8 X-Pos 9 X-Pos 10 Y-Pos. (1,1): FIG. (1, 2): FIG. (1, 3): FIG. (1, 4): FIG. (1, 5): FIG. (1, 6): (1,7): (1, 8): (1, 9): (1, 10): 1 1-A 1-B 1-C 1-D 1-E FIG. 1-F FIG. 1-GFIG. 1-H FIG. 1-I FIG. 1-J Y-Pos. (2, 1): FIG. (2, 2): FIG. (2, 3): FIG.(2, 4): FIG. (2, 5): FIG. (2, 6): (2, 7): (2, 8): (2, 9): (2, 10): 2 1-K1-L 1-M 1-N 1-O FIG. 1-P FIG. 1-Q FIG. 1-R FIG. 1-S FIG. 1-T Y-Pos. (3,1): FIG. (3, 2): FIG. (3, 3): FIG. (3, 4): FIG. (3, 5): FIG. (3, 6): (3,7): FIG. (3, 8): FIG. (3, 9): FIG. (3, 10): 3 1-U 1-V 1-W 1-X 1-Y FIG.1-Z 1-AA 1-AB 1-AC FIG. 1-AD Y-Pos. (4, 1): FIG. (4, 2): FIG. (4, 3):FIG. (4, 3): FIG. (4, 5): FIG. (4, 6): (4, 7): FIG. (4, 8): FIG. (4, 8):FIG. (4, 10): 4 1-AE 1-AF 1-AG 1-AH 1-AI FIG. 1-AJ 1-AK 1-AL 1-AM FIG.1-AN

In accordance with 37 C.F.R. §1.84(h)(2), FIG. 1 is “ . . . a view of alarge machine or device in its entirety . . . broken into partial views. . . extended over several sheets . . . [with] no loss in facility ofunderstanding the view.” The partial views drawn on the several sheetsindicated in the above table are capable of being linked edge to edge,so that no partial view contains parts of another partial view. As here,“where views on two or more sheets form, in effect, a single completeview, the views on the several sheets are so arranged that the completefigure can be assembled without concealing any part of any of the viewsappearing on the various sheets.” 37 C.F.R. §1.84(h)(2).

It is noted that one or more of the partial views of the drawings may beblank, or may be absent of substantive elements (e.g., may show onlylines, connectors, arrows, and/or the like). These drawings are includedin order to assist readers of the application in assembling the singlecomplete view from the partial sheet format required for submission bythe USPTO, and, while their inclusion is not required and may be omittedin this or other applications without subtracting from the disclosedmatter as a whole, their inclusion is proper, and should be consideredand treated as intentional.

FIG. 1-A, when placed at position (1,1), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-B, when placed at position (1,2), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-C, when placed at position (1,3), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-D, when placed at position (1,4), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-E, when placed at position (1,5), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-F, when placed at position (1,6), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-G, when placed at position (1,7), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-H, when placed at position (1,8), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-I, when placed at position (1,9), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-J, when placed at position (1,10), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-K, when placed at position (2,1), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-L, when placed at position (2,2), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-M, when placed at position (2,3), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-N, when placed at position (2,4), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-O (which format is changed to avoid confusion as Figure “10” or“ten”), when placed at position (2,5), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-P, when placed at position (2,6), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-Q, when placed at position (2,7), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-R, when placed at position (2,8), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-S, when placed at position (2,9), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-T, when placed at position (2,10), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-U, when placed at position (3,1), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-V, when placed at position (3,2), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-W, when placed at position (3,3), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-X, when placed at position (3,4), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-Y, when placed at position (3,5), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-Z, when placed at position (3,6), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-AA, when placed at position (3,7), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-AB, when placed at position (3,8), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-AC, when placed at position (3,9), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-AD, when placed at position (3,10), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-AE, when placed at position (4,1), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-AF, when placed at position (4,2), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-AG, when placed at position (4,3), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-AH, when placed at position (4,4), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-AI, when placed at position (4,5), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-AJ, when placed at position (4,6), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-AK, when placed at position (4,7), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-AL, when placed at position (4,8), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-AM, when placed at position (4,9), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-AN, when placed at position (4,10), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 2A shows a high-level block diagram of an exemplary environment200, including an image device 220, according to one or moreembodiments.

FIG. 2B shows a high-level block diagram of a computing device, e.g., aserver device 230 operating in an exemplary environment 200, accordingto one or more embodiments.

FIG. 3A shows a high-level block diagram of an exemplary operation of adevice 220A in an exemplary environment 300A, according to embodiments.

FIG. 3B shows a high-level block diagram of an exemplary operation of adevice 220B in an exemplary environment 300B, according to embodiments.

FIG. 3C shows a high-level block diagram of an exemplary operation of adevice 220C in an exemplary environment 300C, according to embodiments.

FIG. 4A shows a high-level block diagram of an exemplary operation of animage device 420 in an exemplary environment 400A, according toembodiments.

FIG. 4B shows a high-level block diagram of an exemplary operation of animage device 420B in an exemplary environment 400B, according toembodiments.

FIG. 5A shows a high-level block diagram of an exemplary operation of aserver device 530A in an exemplary environment 500A, according toembodiments.

FIG. 5B shows a high-level block diagram of an exemplary operation of aserver device 530B in an exemplary environment 500B, according toembodiments.

FIG. 6, including FIGS. 6A-6G, shows a particular perspective of arequest for particular image data that is part of a scene acquiringmodule 252 of processing module 250 of server device 230 of FIG. 2B,according to an embodiment.

FIG. 7, including FIGS. 7A-7E, shows a particular perspective of arequest for particular image data transmitting to an image sensor arraymodule 254 of processing module 250 of server device 230 of FIG. 2B,according to an embodiment.

FIG. 8, including FIGS. 8A-8C, shows a particular perspective of aparticular image data from the image sensor array exclusive receivingmodule 256 of processing module 250 of server device 230 of FIG. 2B,according to an embodiment.

FIG. 9, including FIGS. 9A-9E, shows a particular perspective of areceived particular image data transmitting to at least one requestormodule 258 of processing module 250 of server device 230 of FIG. 2B,according to an embodiment.

FIG. 10 is a high-level logic flowchart of a process, e g., operationalflow 1000, including one or more operations of an acquiring a requestfor particular image data that is part of a scene operation, atransmitting the request for the particular image data to an imagesensor array operation, a receiving only the particular image data fromthe image sensor array operation, and a transmitting the receivedparticular image data to at least one requestor operation, according toan embodiment.

FIG. 11A is a high-level logic flow chart of a process depictingalternate implementations of an acquiring a request for particular imagedata that is part of a scene operation 1002, according to one or moreembodiments.

FIG. 11B is a high-level logic flow chart of a process depictingalternate implementations of an acquiring a request for particular imagedata that is part of a scene operation 1002, according to one or moreembodiments.

FIG. 11C is a high-level logic flow chart of a process depictingalternate implementations of an acquiring a request for particular imagedata that is part of a scene operation 1002, according to one or moreembodiments.

FIG. 11D is a high-level logic flow chart of a process depictingalternate implementations of an acquiring a request for particular imagedata that is part of a scene operation 1002, according to one or moreembodiments.

FIG. 11E is a high-level logic flow chart of a process depictingalternate implementations of an acquiring a request for particular imagedata that is part of a scene operation 1002, according to one or moreembodiments.

FIG. 11F is a high-level logic flow chart of a process depictingalternate implementations of an acquiring a request for particular imagedata that is part of a scene operation 1002, according to one or moreembodiments.

FIG. 11G is a high-level logic flow chart of a process depictingalternate implementations of an acquiring a request for particular imagedata that is part of a scene operation 1002, according to one or moreembodiments.

FIG. 12A is a high-level logic flow chart of a process depictingalternate implementations of a transmitting the request for theparticular image data to an image sensor array operation 1004, accordingto one or more embodiments.

FIG. 12B is a high-level logic flow chart of a process depictingalternate implementations of a transmitting the request for theparticular image data to an image sensor array operation 1004, accordingto one or more embodiments.

FIG. 12C is a high-level logic flow chart of a process depictingalternate implementations of a transmitting the request for theparticular image data to an image sensor array operation 1004, accordingto one or more embodiments.

FIG. 12D is a high-level logic flow chart of a process depictingalternate implementations of a transmitting the request for theparticular image data to an image sensor array operation 1004, accordingto one or more embodiments.

FIG. 12E is a high-level logic flow chart of a process depictingalternate implementations of a transmitting the request for theparticular image data to an image sensor array operation 1004, accordingto one or more embodiments.

FIG. 13A is a high-level logic flow chart of a process depictingalternate implementations of a receiving only the particular image datafrom the image sensor array operation 1006, according to one or moreembodiments.

FIG. 13B is a high-level logic flow chart of a process depictingalternate implementations of a receiving only the particular image datafrom the image sensor array operation 1006, according to one or moreembodiments.

FIG. 13C is a high-level logic flow chart of a process depictingalternate implementations of a receiving only the particular image datafrom the image sensor array operation 1006, according to one or moreembodiments.

FIG. 14A is a high-level logic flow chart of a process depictingalternate implementations of a transmitting the received particularimage data to at least one requestor operation 1008, according to one ormore embodiments.

FIG. 14B is a high-level logic flow chart of a process depictingalternate implementations of a transmitting the received particularimage data to at least one requestor operation 1008, according to one ormore embodiments.

FIG. 14C is a high-level logic flow chart of a process depictingalternate implementations of a transmitting the received particularimage data to at least one requestor operation 1008, according to one ormore embodiments.

FIG. 14D is a high-level logic flow chart of a process depictingalternate implementations of a transmitting the received particularimage data to at least one requestor operation 1008, according to one ormore embodiments.

FIG. 14E is a high-level logic flow chart of a process depictingalternate implementations of a transmitting the received particularimage data to at least one requestor operation 1008, according to one ormore embodiments.

DETAILED DESCRIPTION Overview

In the following detailed description, reference is made to theaccompanying drawings, which form a part hereof. In the drawings,similar symbols typically identify similar or identical components oritems, unless context dictates otherwise. The illustrative embodimentsdescribed in the detailed description, drawings, and claims are notmeant to be limiting. Other embodiments may be utilized, and otherchanges may be made, without departing from the spirit or scope of thesubject matter presented here.

Thus, in accordance with various embodiments, computationallyimplemented methods, systems, circuitry, articles of manufacture,ordered chains of matter, and computer program products are designed to,among other things, provide an interface for acquiring a request forparticular image data that is part of a scene, transmitting the requestfor the particular image data to an image sensor array that includesmore than one image sensor and that is configured to capture the scenethat is larger than the requested particular image data, and receivingonly the particular image data from the image sensor array.

The claims, description, and drawings of this application may describeone or more of the instant technologies in operational/functionallanguage, for example as a set of operations to be performed by acomputer. Such operational/functional description in most instanceswould be understood by one skilled the art as specifically-configuredhardware (e.g., because a general purpose computer in effect becomes aspecial purpose computer once it is programmed to perform particularfunctions pursuant to instructions from program software (e.g., ahigh-level computer program serving as a hardware specification)).

The claims, description, and drawings of this application may describeone or more of the instant technologies in operational/functionallanguage, for example as a set of operations to be performed by acomputer. Such operational/functional description in most instanceswould be understood by one skilled the art as specifically-configuredhardware (e.g., because a general purpose computer in effect becomes aspecial purpose computer once it is programmed to perform particularfunctions pursuant to instructions from program software).

Operational/Functional Language is a Concrete Specification for PhysicalImplementation

Importantly, although the operational/functional descriptions describedherein are understandable by the human mind, they are not abstract ideasof the operations/functions divorced from computational implementationof those operations/functions. Rather, the operations/functionsrepresent a specification for the massively complex computationalmachines or other means. As discussed in detail below, theoperational/functional language must be read in its proper technologicalcontext, i.e., as concrete specifications for physical implementations.

The logical operations/functions described herein are a distillation ofmachine specifications or other physical mechanisms specified by theoperations/functions such that the otherwise inscrutable machinespecifications may be comprehensible to the human mind. The distillationalso allows one of skill in the art to adapt the operational/functionaldescription of the technology across many different specific vendors'hardware configurations or platforms, without being limited to specificvendors' hardware configurations or platforms.

Some of the present technical description (e.g., detailed description,drawings, claims, etc.) may be set forth in terms of logicaloperations/functions. As described in more detail in the followingparagraphs, these logical operations/functions are not representationsof abstract ideas, but rather representative of static or sequencedspecifications of various hardware elements. Differently stated, unlesscontext dictates otherwise, the logical operations/functions will beunderstood by those of skill in the art to be representative of staticor sequenced specifications of various hardware elements. This is truebecause tools available to one of skill in the art to implementtechnical disclosures set forth in operational/functional formats—toolsin the form of a high-level programming language (e.g., C, java, visualbasic), etc.), or tools in the form of Very high speed HardwareDescription Language (“VHDL,” which is a language that uses text todescribe logic circuits)—are generators of static or sequencedspecifications of various hardware configurations. This fact issometimes obscured by the broad term “software,” but, as shown by thefollowing explanation, those skilled in the art understand that what istermed “software” is a shorthand for a massively complexinterchaining/specification of ordered-matter elements. The term“ordered-matter elements” may refer to physical components ofcomputation, such as assemblies of electronic logic gates, molecularcomputing logic constituents, quantum computing mechanisms, etc.

For example, a high-level programming language is a programming languagewith strong abstraction, e.g., multiple levels of abstraction, from thedetails of the sequential organizations, states, inputs, outputs, etc.,of the machines that a high-level programming language actuallyspecifies. In order to facilitate human comprehension, in manyinstances, high-level programming languages resemble or even sharesymbols with natural languages.

It has been argued that because high-level programming languages usestrong abstraction (e.g., that they may resemble or share symbols withnatural languages), they are therefore a “purely mental construct”(e.g., that “software”—a computer program or computer programming—issomehow an ineffable mental construct, because at a high level ofabstraction, it can be conceived and understood in the human mind). Thisargument has been used to characterize technical description in the formof functions/operations as somehow “abstract ideas.” In fact, intechnological arts (e.g., the information and communicationtechnologies) this is not true.

The fact that high-level programming languages use strong abstraction tofacilitate human understanding should not be taken as an indication thatwhat is expressed is an abstract idea. In fact, those skilled in the artunderstand that just the opposite is true. If a high-level programminglanguage is the tool used to implement a technical disclosure in theform of functions/operations, those skilled in the art will recognizethat, far from being abstract, imprecise, “fuzzy,” or “mental” in anysignificant semantic sense, such a tool is instead a nearincomprehensibly precise sequential specification of specificcomputational machines—the parts of which are built up byactivating/selecting such parts from typically more generalcomputational machines over time (e.g., clocked time). This fact issometimes obscured by the superficial similarities between high-levelprogramming languages and natural languages. These superficialsimilarities also may cause a glossing over of the fact that high-levelprogramming language implementations ultimately perform valuable work bycreating/controlling many different computational machines.

The many different computational machines that a high-level programminglanguage specifies are almost unimaginably complex. At base, thehardware used in the computational machines typically consists of sometype of ordered matter (e.g., traditional electronic devices (e.g.,transistors), deoxyribonucleic acid (DNA), quantum devices, mechanicalswitches, optics, fluidics, pneumatics, optical devices (e.g., opticalinterference devices), molecules, etc.) that are arranged to form logicgates. Logic gates are typically physical devices that may beelectrically, mechanically, chemically, or otherwise driven to changephysical state in order to create a physical reality of Boolean logic.

Logic gates may be arranged to form logic circuits, which are typicallyphysical devices that may be electrically, mechanically, chemically, orotherwise driven to create a physical reality of certain logicalfunctions. Types of logic circuits include such devices as multiplexers,registers, arithmetic logic units (ALUs), computer memory, etc., eachtype of which may be combined to form yet other types of physicaldevices, such as a central processing unit (CPU)—the best known of whichis the microprocessor. A modern microprocessor will often contain morethan one hundred million logic gates in its many logic circuits (andoften more than a billion transistors).

The logic circuits forming the microprocessor are arranged to provide amicroarchitecture that will carry out the instructions defined by thatmicroprocessor's defined Instruction Set Architecture. The InstructionSet Architecture is the part of the microprocessor architecture relatedto programming, including the native data types, instructions,registers, addressing modes, memory architecture, interrupt andexception handling, and external Input/Output.

The Instruction Set Architecture includes a specification of the machinelanguage that can be used by programmers to use/control themicroprocessor. Since the machine language instructions are such thatthey may be executed directly by the microprocessor, typically theyconsist of strings of binary digits, or bits. For example, a typicalmachine language instruction might be many bits long (e.g., 32, 64, or128 bit strings are currently common). A typical machine languageinstruction might take the form “11110000101011110000111100111111” (a 32bit instruction).

It is significant here that, although the machine language instructionsare written as sequences of binary digits, in actuality those binarydigits specify physical reality. For example, if certain semiconductorsare used to make the operations of Boolean logic a physical reality, theapparently mathematical bits “1” and “0” in a machine languageinstruction actually constitute shorthand that specifies the applicationof specific voltages to specific wires. For example, in somesemiconductor technologies, the binary number “1” (e.g., logical “1”) ina machine language instruction specifies around +5 volts applied to aspecific “wire” (e.g., metallic traces on a printed circuit board) andthe binary number “0” (e.g., logical “0”) in a machine languageinstruction specifies around −5 volts applied to a specific “wire.” Inaddition to specifying voltages of the machines' configuration, suchmachine language instructions also select out and activate specificgroupings of logic gates from the millions of logic gates of the moregeneral machine. Thus, far from abstract mathematical expressions,machine language instruction programs, even though written as a stringof zeros and ones, specify many, many constructed physical machines orphysical machine states.

Machine language is typically incomprehensible by most humans (e.g., theabove example was just ONE instruction, and some personal computersexecute more than two billion instructions every second). Thus, programswritten in machine language—which may be tens of millions of machinelanguage instructions long—are incomprehensible. In view of this, earlyassembly languages were developed that used mnemonic codes to refer tomachine language instructions, rather than using the machine languageinstructions' numeric values directly (e.g., for performing amultiplication operation, programmers coded the abbreviation “mult,”which represents the binary number “011000” in MIPS machine code). Whileassembly languages were initially a great aid to humans controlling themicroprocessors to perform work, in time the complexity of the work thatneeded to be done by the humans outstripped the ability of humans tocontrol the microprocessors using merely assembly languages.

At this point, it was noted that the same tasks needed to be done overand over, and the machine language necessary to do those repetitivetasks was the same. In view of this, compilers were created. A compileris a device that takes a statement that is more comprehensible to ahuman than either machine or assembly language, such as “add 2+2 andoutput the result,” and translates that human understandable statementinto a complicated, tedious, and immense machine language code (e.g.,millions of 32, 64, or 128 bit length strings). Compilers thus translatehigh-level programming language into machine language.

This compiled machine language, as described above, is then used as thetechnical specification which sequentially constructs and causes theinteroperation of many different computational machines such thathumanly useful, tangible, and concrete work is done. For example, asindicated above, such machine language—the compiled version of thehigher-level language—functions as a technical specification whichselects out hardware logic gates, specifies voltage levels, voltagetransition timings, etc., such that the humanly useful work isaccomplished by the hardware.

Thus, a functional/operational technical description, when viewed by oneof skill in the art, is far from an abstract idea. Rather, such afunctional/operational technical description, when understood throughthe tools available in the art such as those just described, is insteadunderstood to be a humanly understandable representation of a hardwarespecification, the complexity and specificity of which far exceeds thecomprehension of most any one human. With this in mind, those skilled inthe art will understand that any such operational/functional technicaldescriptions—in view of the disclosures herein and the knowledge ofthose skilled in the art—may be understood as operations made intophysical reality by (a) one or more interchained physical machines, (b)interchained logic gates configured to create one or more physicalmachine(s) representative of sequential/combinatorial logic(s), (c)interchained ordered matter making up logic gates (e.g., interchainedelectronic devices (e.g., transistors), DNA, quantum devices, mechanicalswitches, optics, fluidics, pneumatics, molecules, etc.) that createphysical reality representative of logic(s), or (d) virtually anycombination of the foregoing. Indeed, any physical object which has astable, measurable, and changeable state may be used to construct amachine based on the above technical description. Charles Babbage, forexample, constructed the first computer out of wood and powered bycranking a handle.

Thus, far from being understood as an abstract idea, those skilled inthe art will recognize a functional/operational technical description asa humanly-understandable representation of one or more almostunimaginably complex and time sequenced hardware instantiations. Thefact that functional/operational technical descriptions might lendthemselves readily to high-level computing languages (or high-levelblock diagrams for that matter) that share some words, structures,phrases, etc. with natural language simply cannot be taken as anindication that such functional/operational technical descriptions areabstract ideas, or mere expressions of abstract ideas. In fact, asoutlined herein, in the technological arts this is simply not true. Whenviewed through the tools available to those of skill in the art, suchfunctional/operational technical descriptions are seen as specifyinghardware configurations of almost unimaginable complexity.

As outlined above, the reason for the use of functional/operationaltechnical descriptions is at least twofold. First, the use offunctional/operational technical descriptions allows near-infinitelycomplex machines and machine operations arising from interchainedhardware elements to be described in a manner that the human mind canprocess (e.g., by mimicking natural language and logical narrativeflow). Second, the use of functional/operational technical descriptionsassists the person of skill in the art in understanding the describedsubject matter by providing a description that is more or lessindependent of any specific vendor's piece(s) of hardware.

The use of functional/operational technical descriptions assists theperson of skill in the art in understanding the described subject mattersince, as is evident from the above discussion, one could easily,although not quickly, transcribe the technical descriptions set forth inthis document as trillions of ones and zeroes, billions of single linesof assembly-level machine code, millions of logic gates, thousands ofgate arrays, or any number of intermediate levels of abstractions.However, if any such low-level technical descriptions were to replacethe present technical description, a person of skill in the art couldencounter undue difficulty in implementing the disclosure, because sucha low-level technical description would likely add complexity without acorresponding benefit (e.g., by describing the subject matter utilizingthe conventions of one or more vendor-specific pieces of hardware).Thus, the use of functional/operational technical descriptions assiststhose of skill in the art by separating the technical descriptions fromthe conventions of any vendor-specific piece of hardware.

In view of the foregoing, the logical operations/functions set forth inthe present technical description are representative of static orsequenced specifications of various ordered-matter elements, in orderthat such specifications may be comprehensible to the human mind andadaptable to create many various hardware configurations. The logicaloperations/functions disclosed herein should be treated as such, andshould not be disparagingly characterized as abstract ideas merelybecause the specifications they represent are presented in a manner thatone of skill in the art can readily understand and apply in a mannerindependent of a specific vendor's hardware implementation.

Those having skill in the art will recognize that the state of the arthas progressed to the point where there is little distinction leftbetween hardware, software (e.g., a high-level computer program servingas a hardware specification), and/or firmware implementations of aspectsof systems; the use of hardware, software, and/or firmware is generally(but not always, in that in certain contexts the choice between hardwareand software can become significant) a design choice representing costvs. efficiency tradeoffs. Those having skill in the art will appreciatethat there are various vehicles by which processes and/or systems and/orother technologies described herein can be effected (e.g., hardware,software (e.g., a high-level computer program serving as a hardwarespecification), and/or firmware), and that the preferred vehicle willvary with the context in which the processes and/or systems and/or othertechnologies are deployed. For example, if an implementer determinesthat speed and accuracy are paramount, the implementer may opt for amainly hardware and/or firmware vehicle; alternatively, if flexibilityis paramount, the implementer may opt for a mainly software (e.g., ahigh-level computer program serving as a hardware specification)implementation; or, yet again alternatively, the implementer may opt forsome combination of hardware, software (e.g., a high-level computerprogram serving as a hardware specification), and/or firmware in one ormore machines, compositions of matter, and articles of manufacture,limited to patentable subject matter under 35 USC 101. Hence, there areseveral possible vehicles by which the processes and/or devices and/orother technologies described herein may be effected, none of which isinherently superior to the other in that any vehicle to be utilized is achoice dependent upon the context in which the vehicle will be deployedand the specific concerns (e.g., speed, flexibility, or predictability)of the implementer, any of which may vary. Those skilled in the art willrecognize that optical aspects of implementations will typically employoptically-oriented hardware, software (e.g., a high-level computerprogram serving as a hardware specification), and or firmware.

In some implementations described herein, logic and similarimplementations may include computer programs or other controlstructures. Electronic circuitry, for example, may have one or morepaths of electrical current constructed and arranged to implementvarious functions as described herein. In some implementations, one ormore media may be configured to bear a device-detectable implementationwhen such media holds or transmits device detectable instructionsoperable to perform as described herein. In some variants, for example,implementations may include an update or modification of existingsoftware (e.g., a high-level computer program serving as a hardwarespecification) or firmware, or of gate arrays or programmable hardware,such as by performing a reception of or a transmission of one or moreinstructions in relation to one or more operations described herein.Alternatively or additionally, in some variants, an implementation mayinclude special-purpose hardware, software (e.g., a high-level computerprogram serving as a hardware specification), firmware components,and/or general-purpose components executing or otherwise invokingspecial-purpose components. Specifications or other implementations maybe transmitted by one or more instances of tangible transmission mediaas described herein, optionally by packet transmission or otherwise bypassing through distributed media at various times.

Alternatively or additionally, implementations may include executing aspecial-purpose instruction sequence or invoking circuitry for enabling,triggering, coordinating, requesting, or otherwise causing one or moreoccurrences of virtually any functional operation described herein. Insome variants, operational or other logical descriptions herein may beexpressed as source code and compiled or otherwise invoked as anexecutable instruction sequence. In some contexts, for example,implementations may be provided, in whole or in part, by source code,such as C++, or other code sequences. In other implementations, sourceor other code implementation, using commercially available and/ortechniques in the art, may be compiled//implemented/translated/convertedinto a high-level descriptor language (e.g., initially implementingdescribed technologies in C or C++ programming language and thereafterconverting the programming language implementation into alogic-synthesizable language implementation, a hardware descriptionlanguage implementation, a hardware design simulation implementation,and/or other such similar mode(s) of expression). For example, some orall of a logical expression (e.g., computer programming languageimplementation) may be manifested as a Verilog-type hardware description(e.g., via Hardware Description Language (HDL) and/or Very High SpeedIntegrated Circuit Hardware Descriptor Language (VHDL)) or othercircuitry model which may then be used to create a physicalimplementation having hardware (e.g., an Application Specific IntegratedCircuit). Those skilled in the art will recognize how to obtain,configure, and optimize suitable transmission or computational elements,material supplies, actuators, or other structures in light of theseteachings.

The term module, as used in the foregoing/following disclosure, mayrefer to a collection of one or more components that are arranged in aparticular manner, or a collection of one or more general-purposecomponents that may be configured to operate in a particular manner atone or more particular points in time, and/or also configured to operatein one or more further manners at one or more further times. Forexample, the same hardware, or same portions of hardware, may beconfigured/reconfigured in sequential/parallel time(s) as a first typeof module (e.g., at a first time), as a second type of module (e.g., ata second time, which may in some instances coincide with, overlap, orfollow a first time), and/or as a third type of module (e.g., at a thirdtime which may, in some instances, coincide with, overlap, or follow afirst time and/or a second time), etc. Reconfigurable and/orcontrollable components (e.g., general purpose processors, digitalsignal processors, field programmable gate arrays, etc.) are capable ofbeing configured as a first module that has a first purpose, then asecond module that has a second purpose and then, a third module thathas a third purpose, and so on. The transition of a reconfigurableand/or controllable component may occur in as little as a fewnanoseconds, or may occur over a period of minutes, hours, or days.

In some such examples, at the time the component is configured to carryout the second purpose, the component may no longer be capable ofcarrying out that first purpose until it is reconfigured. A componentmay switch between configurations as different modules in as little as afew nanoseconds. A component may reconfigure on-the-fly, e.g., thereconfiguration of a component from a first module into a second modulemay occur just as the second module is needed. A component mayreconfigure in stages, e.g., portions of a first module that are nolonger needed may reconfigure into the second module even before thefirst module has finished its operation. Such reconfigurations may occurautomatically, or may occur through prompting by an external source,whether that source is another component, an instruction, a signal, acondition, an external stimulus, or similar.

For example, a central processing unit of a personal computer may, atvarious times, operate as a module for displaying graphics on a screen,a module for writing data to a storage medium, a module for receivinguser input, and a module for multiplying two large prime numbers, byconfiguring its logical gates in accordance with its instructions. Suchreconfiguration may be invisible to the naked eye, and in someembodiments may include activation, deactivation, and/or re-routing ofvarious portions of the component, e.g., switches, logic gates, inputs,and/or outputs. Thus, in the examples found in the foregoing/followingdisclosure, if an example includes or recites multiple modules, theexample includes the possibility that the same hardware may implementmore than one of the recited modules, either contemporaneously or atdiscrete times or timings. The implementation of multiple modules,whether using more components, fewer components, or the same number ofcomponents as the number of modules, is merely an implementation choiceand does not generally affect the operation of the modules themselves.Accordingly, it should be understood that any recitation of multiplediscrete modules in this disclosure includes implementations of thosemodules as any number of underlying components, including, but notlimited to, a single component that reconfigures itself over time tocarry out the functions of multiple modules, and/or multiple componentsthat similarly reconfigure, and/or special purpose reconfigurablecomponents.

Those skilled in the art will recognize that it is common within the artto implement devices and/or processes and/or systems, and thereafter useengineering and/or other practices to integrate such implemented devicesand/or processes and/or systems into more comprehensive devices and/orprocesses and/or systems. That is, at least a portion of the devicesand/or processes and/or systems described herein can be integrated intoother devices and/or processes and/or systems via a reasonable amount ofexperimentation. Those having skill in the art will recognize thatexamples of such other devices and/or processes and/or systems mightinclude—as appropriate to context and application—all or part of devicesand/or processes and/or systems of (a) an air conveyance (e.g., anairplane, rocket, helicopter, etc.), (b) a ground conveyance (e.g., acar, truck, locomotive, tank, armored personnel carrier, etc.), (c) abuilding (e.g., a home, warehouse, office, etc.), (d) an appliance(e.g., a refrigerator, a washing machine, a dryer, etc.), (e) acommunications system (e.g., a networked system, a telephone system, aVoice over IP system, etc.), (f) a business entity (e.g., an InternetService Provider (ISP) entity such as Comcast Cable, Qwest, SouthwesternBell, etc.), or (g) a wired/wireless services entity (e.g., Sprint,Cingular, Nextel, etc.), etc.

In certain cases, use of a system or method may occur in a territoryeven if components are located outside the territory. For example, in adistributed computing context, use of a distributed computing system mayoccur in a territory even though parts of the system may be locatedoutside of the territory (e.g., relay, server, processor, signal-bearingmedium, transmitting computer, receiving computer, etc. located outsidethe territory).

A sale of a system or method may likewise occur in a territory even ifcomponents of the system or method are located and/or used outside theterritory. Further, implementation of at least part of a system forperforming a method in one territory does not preclude use of the systemin another territory

In a general sense, those skilled in the art will recognize that thevarious embodiments described herein can be implemented, individuallyand/or collectively, by various types of electro-mechanical systemshaving a wide range of electrical components such as hardware, software,firmware, and/or virtually any combination thereof, limited topatentable subject matter under 35 U.S.C. 101; and a wide range ofcomponents that may impart mechanical force or motion such as rigidbodies, spring or torsional bodies, hydraulics, electro-magneticallyactuated devices, and/or virtually any combination thereof.Consequently, as used herein “electro-mechanical system” includes, butis not limited to, electrical circuitry operably coupled with atransducer (e.g., an actuator, a motor, a piezoelectric crystal, a MicroElectro Mechanical System (MEMS), etc.), electrical circuitry having atleast one discrete electrical circuit, electrical circuitry having atleast one integrated circuit, electrical circuitry having at least oneapplication specific integrated circuit, electrical circuitry forming ageneral purpose computing device configured by a computer program (e.g.,a general purpose computer configured by a computer program which atleast partially carries out processes and/or devices described herein,or a microprocessor configured by a computer program which at leastpartially carries out processes and/or devices described herein),electrical circuitry forming a memory device (e.g., forms of memory(e.g., random access, flash, read only, etc.)), electrical circuitryforming a communications device (e.g., a modem, communications switch,optical-electrical equipment, etc.), and/or any non-electrical analogthereto, such as optical or other analogs (e.g., graphene basedcircuitry). Those skilled in the art will also appreciate that examplesof electro-mechanical systems include, but are not limited to, a varietyof consumer electronics systems, medical devices, as well as othersystems such as motorized transport systems, factory automation systems,security systems, and/or communication/computing systems. Those skilledin the art will recognize that electro-mechanical as used herein is notnecessarily limited to a system that has both electrical and mechanicalactuation except as context may dictate otherwise.

In a general sense, those skilled in the art will recognize that thevarious aspects described herein which can be implemented, individuallyand/or collectively, by a wide range of hardware, software, firmware,and/or any combination thereof can be viewed as being composed ofvarious types of “electrical circuitry.” Consequently, as used herein“electrical circuitry” includes, but is not limited to, electricalcircuitry having at least one discrete electrical circuit, electricalcircuitry having at least one integrated circuit, electrical circuitryhaving at least one application specific integrated circuit, electricalcircuitry forming a general purpose computing device configured by acomputer program (e.g., a general purpose computer configured by acomputer program which at least partially carries out processes and/ordevices described herein, or a microprocessor configured by a computerprogram which at least partially carries out processes and/or devicesdescribed herein), electrical circuitry forming a memory device (e.g.,forms of memory (e.g., random access, flash, read only, etc.)), and/orelectrical circuitry forming a communications device (e.g., a modem,communications switch, optical-electrical equipment, etc.). Those havingskill in the art will recognize that the subject matter described hereinmay be implemented in an analog or digital fashion or some combinationthereof.

Those skilled in the art will recognize that at least a portion of thedevices and/or processes described herein can be integrated into animage processing system. Those having skill in the art will recognizethat a typical image processing system generally includes one or more ofa system unit housing, a video display device, memory such as volatileor non-volatile memory, processors such as microprocessors or digitalsignal processors, computational entities such as operating systems,drivers, applications programs, one or more interaction devices (e.g., atouch pad, a touch screen, an antenna, etc.), control systems includingfeedback loops and control motors (e.g., feedback for sensing lensposition and/or velocity; control motors for moving/distorting lenses togive desired focuses). An image processing system may be implementedutilizing suitable commercially available components, such as thosetypically found in digital still systems and/or digital motion systems.

Those skilled in the art will recognize that at least a portion of thedevices and/or processes described herein can be integrated into a dataprocessing system. Those having skill in the art will recognize that adata processing system generally includes one or more of a system unithousing, a video display device, memory such as volatile or non-volatilememory, processors such as microprocessors or digital signal processors,computational entities such as operating systems, drivers, graphicaluser interfaces, and applications programs, one or more interactiondevices (e.g., a touch pad, a touch screen, an antenna, etc.), and/orcontrol systems including feedback loops and control motors (e.g.,feedback for sensing position and/or velocity; control motors for movingand/or adjusting components and/or quantities). A data processing systemmay be implemented utilizing suitable commercially available components,such as those typically found in data computing/communication and/ornetwork computing/communication systems.

Those skilled in the art will recognize that at least a portion of thedevices and/or processes described herein can be integrated into a motesystem. Those having skill in the art will recognize that a typical motesystem generally includes one or more memories such as volatile ornon-volatile memories, processors such as microprocessors or digitalsignal processors, computational entities such as operating systems,user interfaces, drivers, sensors, actuators, applications programs, oneor more interaction devices (e.g., an antenna USB ports, acoustic ports,etc.), control systems including feedback loops and control motors(e.g., feedback for sensing or estimating position and/or velocity;control motors for moving and/or adjusting components and/orquantities). A mote system may be implemented utilizing suitablecomponents, such as those found in mote computing/communication systems.Specific examples of such components entail such as Intel Corporation'sand/or Crossbow Corporation's mote components and supporting hardware,software, and/or firmware.

For the purposes of this application, “cloud” computing may beunderstood as described in the cloud computing literature. For example,cloud computing may be methods and/or systems for the delivery ofcomputational capacity and/or storage capacity as a service. The “cloud”may refer to one or more hardware and/or software components thatdeliver or assist in the delivery of computational and/or storagecapacity, including, but not limited to, one or more of a client, anapplication, a platform, an infrastructure, and/or a server. The cloudmay refer to any of the hardware and/or software associated with aclient, an application, a platform, an infrastructure, and/or a server.For example, cloud and cloud computing may refer to one or more of acomputer, a processor, a storage medium, a router, a switch, a modem, avirtual machine (e.g., a virtual server), a data center, an operatingsystem, a middleware, a firmware, a hardware back-end, a softwareback-end, and/or a software application. A cloud may refer to a privatecloud, a public cloud, a hybrid cloud, and/or a community cloud. A cloudmay be a shared pool of configurable computing resources, which may bepublic, private, semi-private, distributable, scaleable, flexible,temporary, virtual, and/or physical. A cloud or cloud service may bedelivered over one or more types of network, e.g., a mobilecommunication network, and the Internet.

As used in this application, a cloud or a cloud service may include oneor more of infrastructure-as-a-service (“IaaS”), platform-as-a-service(“PaaS”), software-as-a-service (“SaaS”), and/or desktop-as-a-service(“DaaS”). As a non-exclusive example, IaaS may include, e.g., one ormore virtual server instantiations that may start, stop, access, and/orconfigure virtual servers and/or storage centers (e.g., providing one ormore processors, storage space, and/or network resources on-demand,e.g., EMC and Rackspace). PaaS may include, e.g., one or more softwareand/or development tools hosted on an infrastructure (e.g., a computingplatform and/or a solution stack from which the client can createsoftware interfaces and applications, e.g., Microsoft Azure). SaaS mayinclude, e.g., software hosted by a service provider and accessible overa network (e.g., the software for the application and/or the dataassociated with that software application may be kept on the network,e.g., Google Apps, SalesForce). DaaS may include, e.g., providingdesktop, applications, data, and/or services for the user over a network(e.g., providing a multi-application framework, the applications in theframework, the data associated with the applications, and/or servicesrelated to the applications and/or the data over the network, e.g.,Citrix). The foregoing is intended to be exemplary of the types ofsystems and/or methods referred to in this application as “cloud” or“cloud computing” and should not be considered complete or exhaustive.

One skilled in the art will recognize that the herein describedcomponents (e.g., operations), devices, objects, and the discussionaccompanying them are used as examples for the sake of conceptualclarity and that various configuration modifications are contemplated.Consequently, as used herein, the specific exemplars set forth and theaccompanying discussion are intended to be representative of their moregeneral classes. In general, use of any specific exemplar is intended tobe representative of its class, and the non-inclusion of specificcomponents (e.g., operations), devices, and objects should not be takenlimiting.

The herein described subject matter sometimes illustrates differentcomponents contained within, or connected with, different othercomponents. It is to be understood that such depicted architectures aremerely exemplary, and that in fact many other architectures may beimplemented which achieve the same functionality. In a conceptual sense,any arrangement of components to achieve the same functionality iseffectively “associated” such that the desired functionality isachieved. Hence, any two components herein combined to achieve aparticular functionality can be seen as “associated with” each othersuch that the desired functionality is achieved, irrespective ofarchitectures or intermedial components. Likewise, any two components soassociated can also be viewed as being “operably connected”, or“operably coupled,” to each other to achieve the desired functionality,and any two components capable of being so associated can also be viewedas being “operably couplable,” to each other to achieve the desiredfunctionality. Specific examples of operably couplable include, but arenot limited to, physically mateable and/or physically interactingcomponents, and/or wirelessly interactable, and/or wirelesslyinteracting components, and/or logically interacting, and/or logicallyinteractable components.

To the extent that formal outline headings are present in thisapplication, it is to be understood that the outline headings are forpresentation purposes, and that different types of subject matter may bediscussed throughout the application (e.g., device(s)/structure(s) maybe described under process(es)/operations heading(s) and/orprocess(es)/operations may be discussed under structure(s)/process(es)headings; and/or descriptions of single topics may span two or moretopic headings). Hence, any use of formal outline headings in thisapplication is for presentation purposes, and is not intended to be inany way limiting.

Throughout this application, examples and lists are given, withparentheses, the abbreviation “e.g.,” or both. Unless explicitlyotherwise stated, these examples and lists are merely exemplary and arenon-exhaustive. In most cases, it would be prohibitive to list everyexample and every combination. Thus, smaller, illustrative lists andexamples are used, with focus on imparting understanding of the claimterms rather than limiting the scope of such terms.

With respect to the use of substantially any plural and/or singularterms herein, those having skill in the art can translate from theplural to the singular and/or from the singular to the plural as isappropriate to the context and/or application. The varioussingular/plural permutations are not expressly set forth herein for sakeof clarity.

One skilled in the art will recognize that the herein describedcomponents (e.g., operations), devices, objects, and the discussionaccompanying them are used as examples for the sake of conceptualclarity and that various configuration modifications are contemplated.Consequently, as used herein, the specific exemplars set forth and theaccompanying discussion are intended to be representative of their moregeneral classes. In general, use of any specific exemplar is intended tobe representative of its class, and the non-inclusion of specificcomponents (e.g., operations), devices, and objects should not be takenlimiting.

Although one or more users maybe shown and/or described herein, e.g., inFIG. 1, and other places, as a single illustrated figure, those skilledin the art will appreciate that one or more users may be representativeof one or more human users, robotic users (e.g., computational entity),and/or substantially any combination thereof (e.g., a user may beassisted by one or more robotic agents) unless context dictatesotherwise. Those skilled in the art will appreciate that, in general,the same may be said of “sender” and/or other entity-oriented terms assuch terms are used herein unless context dictates otherwise.

In some instances, one or more components may be referred to herein as“configured to,” “configured by,” “configurable to,” “operable/operativeto,” “adapted/adaptable,” “able to,” “conformable/conformed to,” etc.Those skilled in the art will recognize that such terms (e.g.“configured to”) generally encompass active-state components and/orinactive-state components and/or standby-state components, unlesscontext requires otherwise.

High-Level System Architecture

FIG. 1, including FIGS. 1-A-1-AN, shows partial views that, whenassembled, form a complete view of an entire system, of which at least aportion will be described in more detail. An overview of the entiresystem of FIG. 1 is now described herein, with a more specific referenceto at least one subsystem of FIG. 1 to be described later with respectto FIGS. 2-14D.

FIG. 1 shows various implementations of the overall system. At a highlevel, FIG. 1 shows various implementations of a multiple user videoimaging array (hereinafter interchangeably referred to as a “MUVIA”). Itis noted that the designation “MUVIA” is merely shorthand anddescriptive of an exemplary embodiment, and not a limiting term.Although “multiple user” appears in the name MUVIA, multiple users oreven a single user are not required. Further, “video” is used in thedesignation “MUVIA,” but MUVIA systems also may capture still images,multiple images, audio data, electromagnetic waves outside the visiblespectrum, and other data as will be described herein. Further, “imagingarray” may be used in the MUVIA designation, but the image sensor inMUVIA is not necessarily an array or even multiple sensors (althoughcommonly implemented as larger groups of image sensors, single-sensorimplementations are also contemplated), and “array” here does notnecessarily imply any specific structure, but rather any grouping of oneor more sensors.

Generally, although not necessarily required, a MUVIA system may includeone or more of a user device (e.g., hereinafter interchangeably referredto as a “client device,” in recognition that a user may not necessarilybe a human, living, or organic”), a server, and an image sensor array. A“server” in the context of this application may refer to any device,program, or module that is not directly connected to the image sensorarray or to the client device, including any and all “cloud” storage,applications, and/or processing.

For example, in an embodiment, e.g., as shown in FIG. 1-A, FIG. 1-K,FIG. 1-U, FIG. 1-AE, and FIG. 1-AF, in an embodiment, the system mayinclude one or more of image sensor array 3200, array local processingmodule 3300, server 4000, and user device 5200. Each of these portionswill be discussed in more detail herein.

Referring now to FIG. 1-A, FIG. 1-A depicts user device 5200, which is adevice that may be operated or controlled by a user of a MUVIA system.It is noted here that “user” is merely provided as a designation forease of understanding, and does not imply control by a human or otherorganism, sentient or otherwise. In an embodiment, for example, in asecurity-type embodiment, the user device 5200 may be mostly orcompletely unmonitored, or may be monitored by an artificialintelligence, or by a combination of artificial intelligence,pseudo-artificial intelligence (e.g., that is intelligenceamplification) and human intelligence.

User device 5200 may be, but is not limited to, a wearable device (e.g.,glasses, goggles, headgear, a watch, clothing), an implant (e.g., aretinal-implant display), a computer of any kind (e.g., a laptopcomputer, desktop computer, mainframe, server, etc.), a tablet or otherportable device, a phone or other similar device (e.g., smartphone,personal digital assistant), a personal electronic device (e.g., musicplayer, CD player), a home appliance (e.g., a television, arefrigerator, or any other so-called “smart” device), a piece of officeequipment (e.g., a copier, scanner, fax device, etc.), a camera or othercamera-like device, a video game system, an entertainment/media center,or any other electrical equipment that has a functionality of presentingan image (whether visual or by other means, e.g., a screen, but alsoother sensory stimulating work).

User device 5200 may be capable of presenting an image, which, forpurposes of clarity and conciseness will be referred to as displaying animage, although communication through forms other than generating lightwaves through the visible light spectrum, although the image is notrequired to be presented at all times or even at all. For example, in anembodiment, user device 5200 may receive images from server 4000 (ordirectly from the image sensor array 3200, as will be discussed herein),and may store the images for later viewing, or for processinginternally, or for any other reason.

Referring again to FIG. 1-A, in an embodiment, user device 5200 mayinclude a user selection accepting module 5210. User selection acceptingmodule 5210 may be configured to receive user input about what the userwants to see. For example, as shown in FIG. 1-A in the exemplaryinterface 5212, the user selection accepting module 5210 may show animage from image sensor array 3200, and the user may “pan” and “zoom”the image using any known interface, including, but not limited to,keyboard, mouse, touch, haptic, augmented reality interface, voicecommand, nonverbal motion commands (e.g., as part of a video game systeminterface, e.g., the Microsoft Kinect). It is noted, and as will bediscussed in more detail herein, the camera itself is not “zooming” or“panning,” because the camera does not move. What is happening is thatdifferent pixels that are captured by the image sensor array 3200 arekept by the image sensor array 3200 and transmitted to the server 4000.

In an embodiment, the user selection accepting module 5210 may accept aselection of a particular thing—e.g., a building, an animal, or anyother object whose representation is present on the screen. Moreover, auser may use a text box to “search” the image for a particular thing,and processing, done at the user device 5200 or at the server 4000, maydetermine the image and the zoom level for viewing that thing. Thesearch for a particular thing may include a generic search, e.g.,“search for people,” or “search for penguins,” or a more specificsearch, e.g., “search for the Space Needle,” or “search for the WhiteHouse.” The search for a particular thing may take on any knowncontextual search, e.g., an address, a text string, or any other input.

In an embodiment, the “user selection” facilitated by the user selectionaccepting module 5210 may not involve a user at all. For example, in anembodiment, e.g., in a security embodiment, the user selection may behandled completely by machine, and may include “select any portion ofthe image with movement,” or “select any portion of the image in which aperson is recognized,” or “select any portion of the image in which aparticular person, e.g., a person on the FBI most wanted list” isrecognized.

Referring again to FIG. 1-A, in an embodiment, user device 5200 mayinclude a user selection transmitting module 5220. The user selectiontransmitting module 5220 may take the user selection from user selectiontransmitting module 5220, and transmit the selection to the server 4000.The transmission may include some pre-processing, for example, the userdevice 5200 may determine the size and parameters of the image prior tosending the request to the server 4000, or that processing may behandled by the server 4000. Following the thick-line arrow leftward fromuser selection transmitting module 5220 through to FIG. 1-K, thetransmission goes to server 4000, as will be discussed herein. It isnoted that the transmission to the server 4000 may also include dataabout the user device 5200, for example, the screen resolution, thewindow size, the type of device, an identity of the user, a level ofservice the user has paid for (in embodiments in which such services areprioritized by the camera/server), other capabilities of the device,e.g., framerate, and the like.

Referring again to FIG. 1-A, FIG. 1-A also includes a selected imagereceiving module 5230 and a user selection presenting module 5240, whichwill be discussed in more detail herein, with respect to the dataflow ofthis embodiment.

Referring now to FIG. 1-K, FIGS. 1-K and 1-U show an embodiment of aserver 4000 that communicates with one or both of user device 5200 andarray local processing module 3300. Sever 4000 may be a single computingdevice, or may be many computing devices, which may or may not be inproximity with each other.

Referring again to FIG. 1-K, server 4000 may include a user requestreception module 4010. The user request reception module 4010 mayreceive the transmitted request from user selection transmitting module5220. The user request reception module 4010 may then turn overprocessing to user request validation module 4020, which may perform,among other things, a check to make sure the user is not requesting moreresolution than what their device can handle. For example, if the serverhas learned (e.g., through gathered information, or through informationthat was transmitted with the user request or in a same session as theuser request), that the user is requesting a 1900×1080 resolution image,and the maximum resolution for the device is 1334×750, then the requestwill be modified so that no more than the maximum resolution that can behandled by the device is requested. In an embodiment, this may conservethe bandwidth required to transmit from the MUVIA to the server 4000and/or the user device 5200.

Referring again to FIG. 1-K, in an embodiment, server 4000 may include auser request latency management module 4030. User request latencymanagement module 4030 may, in conjunction with user device 5200,attempt to reduce the latency from the time a specific image isrequested by user device 5200 to the time the request is acted upon anddata is transmitted to the user. The details for this latency managementwill be described in more detail herein, with varying techniques thatmay be carried out by any or all of the devices in the chain (e.g., userdevice, camera array, and server). As an example, in an embodiment, alower resolution version of the image, e.g., that is stored locally oron the server, may be sent to the user immediately upon the request, andthen that image is updated with the actual image taken by the camera. Inan embodiment, user request latency management module 4030 also mayhandle static gap-filling, that is, if the image captured by the camerais unchanging, e.g., has not changed for a particular period of time,then a new image is not necessary to be captured, and an older image,that may be stored on server 4000, may be transmitted to the user device5200. This process also will be discussed in more detail herein.

Referring now to FIG. 1-U, which shows more of server 4000, in anembodiment, server 4000 may include a consolidated user requesttransmission module 4040, which may be configured to consolidate all theuser requests, perform any necessary pre-processing on those requests,and send the request for particular sets of pixels to the array localprocessing module 3300. The process for consolidating the user requestsand performing pre-processing will be described in more detail hereinwith respect to some of the other exemplary embodiments. In thisembodiment, however, server consolidated user request transmissionmodule 4040 transmits the request (exiting leftward from FIG. 1-U andtraveling downward to FIG. 1-AE, through a pathway identified in FIG.1-AE as lower-bandwidth communication from remote server to ISA 3515. Itis noted here that “lower bandwidth communication” does not necessarilymean “low bandwidth” or imply any specific number about the bandwidth—itis simply lower than the relatively higher bandwidth communication fromthe actual image sensor array 3505 to the array local processing module3300, which will be discussed in more detail herein.

Referring again to FIG. 1-U, server 4000 also may include requestedpixel reception module 4050, user request preparation module 4060, anduser request transmission module 4070 (shown in FIG. 1-k), which will bediscussed in more detail herein, with respect to the dataflow of thisembodiment

Referring now to FIGS. 1-AE and 1-AF, FIGS. 1-AE and 1-AF show an imagesensor array (“ISA”) 3200 and an array local processing module 3300,each of which will now be described in more detail.

Image sensor array 3200 may include one or more image sensors that may,in an embodiment, be statically pointed at a particular object or scene.Image sensor array 3200 may be a single image sensor, or more commonly,may be a group of individual image sensors 3201 that are combined tocreate a larger field of view. For example, in an embodiment, tenmegapixel sensors may be used for each individual image sensor 3201.With twelve of these sensors, the effective field of view, loss-lesszoom, and so forth may be increased substantially. These numbers are forexample only, and any number of sensors and/or megapixel image sensorcapacities may be used.

The use of many individual sensors may create a very large number ofpixels captured for each exposure of the image sensor array 3200. Thus,these pixels are transmitted via a higher bandwidth communication 3505to the array local processing module 3300. In an embodiment, array localprocessing module 3300 is integrated into the image sensor array 3200.In another embodiment, the array local processing module 3300 isseparate from, but directly connected to (e.g., via a USB 3.0 cable) tothe image sensor array 3200. It is noted that “higher bandwidthcommunication 3505” does not require a specific amount of bandwidth, butonly that the bandwidth for this communication is relatively higher thanthe bandwidth communication from the array local processing module 3300to the remote server, which may be, but is not required to be, locatedfurther away temporally.

It is noted that, because of the large number of pixels captured byimage sensor array 3200, mechanical changes to the image sensor array3200 are not generally required, although such mechanical changes arenot excluded from these embodiments. For example, because the array hasa very large field of view, with very high resolution, “pan” and “zoom”functions may be handled optically, rather than by mechanically changingthe focal point of the lenses or by physically pointing the array at adifferent location. This may reduce the complexity required of thedevice, and also may improve the speed at which different views may begenerated by the image sensor array 3200.

Referring again to FIG. 1-AE, the image sensor array 3300 may capture animage that is received by image capturing module 3305. Image capturingmodule 3305 may take the captured image and compare it to a consolidateduser request, e.g., which is provided by a consolidated user requestreception module 3310. Consolidated user request reception module 3310may receive the communication from server 4000 regarding which pixels ofthe image have been requested. Through use of the consolidated userrequest and the captured image, pixel selection module 3320 may selectthe pixels that have been specifically requested by the user, and markthose pixels for transmission back to the server.

After the pixels to be kept are identified, the other pixels that arenot to be kept are removed, e.g., decimated at unused pixel decimationmodule 3330. In an embodiment, these pixels are simply discarded, e.g.,not stored in a long-term memory, that is removed to a digital trash3317. In another embodiment, some or all of these pixels are stored in alocal memory, e.g., local memory 3315. From here, these pixels may betransmitted to various locations at off-peak times, may be kept forimage processing by the array local processing module 3300, or may besubject to other manipulations or processing separate from the userrequests.

Referring again to FIG. 1-AE, the selected pixels then may betransmitted to the server 4000 using selected pixel transmission module3340. Selected pixel transmission module 3340 may include anytransmission equipment necessary, e.g., cellular radio, wirelessadapter, and the like, depending on the format of communication. In anembodiment, only those pixels which have been requested are transmittedto the server via lower-bandwidth communication 3510. Similarly tolower-bandwidth communication 3515, the lower-bandwidth communication3510 does not refer to a specific amount of bandwidth, just that theamount of bandwidth is relatively lower than higher-bandwidthcommunication 3505.

It is noted that more pixels than what are specifically requested by theuser may be transmitted, in certain embodiments. For example, the arraylocal processing module 3300 may send pixels that border the user'srequested area, but are outside the user's requested area. In anembodiment, as will be discussed herein, those pixels may be sent at adifferent resolution or using a different kind of compression. Inanother embodiment, the additional pixels may merely be sent the same asthe requested pixels. In still another embodiment, server 4000 mayexpand the user requested areas, so that array local processing module3300 may send only the requested pixels, but the requested pixels covermore area than what the user originally requested. These additionalpixels may be transmitted and “cached” by the server or local device,which may be used to decrease latency times, in a process that will bediscussed more herein.

Referring back to FIG. 1-U, the transmitted pixels transmitted fromselected pixel transmission module 3340 of array local processing module3300 may be received by server 4000, e.g., at requested pixel receptionmodule 4050. Requested pixel reception module 4050 may receive therequested pixels and turn them over to user request preparation module4060, which may “unpack” the requested pixels, e.g., determining whichpixels go to which user, and at what resolutions, along with anypost-processing, including image adjustment, adding in missing cacheddata, or adding additional data to the images (e.g., advertisements orother data). In an embodiment, server 4000 also may include a userrequest transmission module 4070, which may be configured to transmitthe requested pixels back to the user device 5200.

Referring again to FIG. 1-A, user device 5200 may include a selectedimage receiving module 5230, which may receive the pixels that were sentby the server 4000, and user selection presenting module 5240, which maydisplay the requested pixels to the user, e.g., by showing them on ascreen of the device. In an embodiment, the display of the image may becarried out through the exemplary interface, which allows a cycle ofuser requests and new images to be shown as the user navigates throughwhat is seen on the MUVIA, e.g., as shown in FIG. 1-A.

FIGS. 1-B, 1-C, 1-M, 1-W, 1-AG, and 1-AH show another embodiment of theMUVIA system, in which multiple user devices 5510, 5520, and 5530 mayrequest images captured by the same image sensor array 3200.

Referring now to FIGS. 1-B and 1-C, user device 5510, user device 5520,and user device 5530 are shown. In an embodiment, user devices 5510,5520, and 5530 may have some or all of the same components as userdevice 5200, but are not shown here for clarity and ease ofunderstanding the drawing. For each of user devices 5510, 5520, and5530, exemplary screen resolutions have been chosen. There is nothingspecific about these numbers that have been chosen, however, they aremerely illustrated for exemplary purposes, and any other numbers couldhave been chosen in their place.

For example, in an embodiment, referring to FIG. 1-B, user device 5510may have a screen resolution of 1920×1080 (e.g., colloquially referredto as “HD quality”). User device 5510 may send an image request to theserver 4000, and may also send data regarding the screen resolution ofthe device.

Referring now to FIG. 1-C, user device 5520 may have a screen resolutionof 1334×750. User device 5520 may send another image request to theserver 4000, and, in an embodiment, instead of sending data regardingthe screen resolution of the device, may send data that identifies whatkind of device it is (e.g., an Apple-branded smartphone). Server 4000may use this data to determine the screen resolution for user device5520 through an internal database, or through contacting an externalsource, e.g., a manufacturer of the device or a third party supplier ofdata about devices.

Referring again to FIG. 1-C, user device 5530 may have a screenresolution of 640×480, and may send the request by itself to the server4000, without any additional data. In addition, server 4000 may receiveindependent requests from various users to change their current viewingarea on the device.

Referring now to FIG. 1-M, server 4000 may include user requestreception module 4110. User request reception module 4110 may receiverequests from multiple user devices, e.g., user devices 5510, 5520, and5530. Server 4000 also may include an independent user view changerequest reception module 4115, which, in an embodiment, may be a part ofuser request reception module 4110, and may be configured to receiverequests from users that are already connected to the system, to changethe view of what they are currently seeing.

Referring again to FIG. 1-M, server 4000 may include relevant pixelselection module 4120 configured to combine the user selections into asingle area, as shown in FIG. 1-M. It is noted that, in an embodiment,the different user devices may request areas that overlap each other. Inthis case, there may be one or more overlapping areas, e.g., overlappingareas 4122. In an embodiment, the overlapping areas are only transmittedonce, in order to save data/transmission costs and increase efficiency.

Referring now to FIG. 1-W, server 4000 may include selected pixeltransmission to ISA module 4130. Module 4130 may take the relevantselected pixels, and transmit them to the array local processing module3400 of image sensor array 3200. Selected pixel transmission to ISAmodule 4130 may include communication components, which may be sharedwith other transmission and/or reception modules.

Referring now to FIG. 1-AG, array local processing module 3400 maycommunicate with image sensor array 3200. Similarly to FIGS. 1-AE and1-AF, FIGS. 1-AG and 1-AH show array local processing module 3400 andimage sensor array 3200, respectively.

Image sensor array 3200 may include one or more image sensors that may,in an embodiment, be statically pointed at a particular object or scene.Image sensor array 3200 may be a single image sensor, or more commonly,may be a group of individual image sensors 3201 that are combined tocreate a larger field of view. For example, in an embodiment, tenmegapixel sensors may be used for each individual image sensor 3201.With twelve of these sensors, the effective field of view, loss-lesszoom, and so forth may be increased substantially. These numbers are forexample only, and any number of sensors and/or megapixel image sensorcapacities may be used.

The use of many individual sensors may create a very large number ofpixels captured for each exposure of the image sensor array 3200. Thus,these pixels are transmitted via a higher bandwidth communication 3505to the array local storage and processing module 3400. In an embodiment,array local storage module 3400 is integrated into the image sensorarray. In another embodiment, the array local storage and processingmodule 3400 is separate from, but directly connected to (e.g., via a USB3.0 cable) to the image sensor array 3200. It is noted that “higherbandwidth communication 3505” does not require a specific amount ofbandwidth, but only that the bandwidth for this communication isrelatively higher than the bandwidth communication from the array localprocessing module 3400 to the remote server, which may be, but is notrequired to be, located further away temporally.

It is noted that, because of the large number of pixels captured byimage sensor array 3200, mechanical changes to the image sensor arrayare not generally required, although such mechanical changes are notexcluded from these embodiments. For example, because the array has avery large field of view, with very high resolution, “pan” and “zoom”functions may be handled optically, rather than by mechanically changingthe focal point of the lenses or by physically pointing the array at adifferent location. This may reduce the complexity required of thedevice, and also may improve the speed at which different views may begenerated by the image sensor array 3200.

Referring again to FIG. 1-AG, the image sensor array 3200 may capture animage and compare it to a consolidated user request, e.g., which isprovided by a consolidated user request reception module 3410.Consolidated user request reception module 3410 may receive thecommunication from server 4000 regarding which pixels of the image havebeen requested. Through use of the consolidated user request and thecaptured image, pixel selection module 3420 may select the pixels thathave been specifically requested by the user, and mark those pixels fortransmission back to the server.

After the pixels to be kept are identified, the other pixels that arenot to be kept are removed, e.g., decimated at unused pixel decimationmodule 3430. In an embodiment, these pixels are simply discarded, e.g.,not stored in a long-term memory, that is removed to a digital trash3417. In another embodiment, some or all of these pixels are stored in alocal memory, e.g., local memory 3415. From here, these pixels may betransmitted to various locations at off-peak times, may be kept forimage processing by the array local processing module 3400, or may besubject to other manipulations or processing separate from the userrequests.

Referring gain to FIG. 1-AG, array local processing module 3400 mayinclude flagged selected pixel transmission module 3440, which takes thepixels identified as requested (e.g., “flagged”) and transmits them backto the server 4000 for further processing. Similarly to as previouslydescribed, this transmission may utilize a lower-bandwidth channel, andmodule 3440 may include all necessary hardware to effect thatlower-bandwidth transmission to server 4000.

Referring again to FIG. 1-W, the flagged selected pixel transmissionmodule 3440 of array local processing module 3400 may transmit theflagged pixels to server 4000. Specifically, flagged selected pixeltransmission module 3440 may transmit the pixels to flagged selectedpixel reception from ISA module 4140 of server 4000, as shown in FIG.1-W.

Referring again to FIG. 1-W, server 4000 also may include flaggedselected pixel separation and duplication module 4150, which may,effectively, reverse the process of combining the pixels from thevarious selections, duplicating overlapping areas where necessary, andcreating the requested images for each of the user devices thatrequested images. Flagged selected pixel separation and duplicationmodule 4150 also may include the post-processing done to the image,including filling in cached versions of images, image adjustments basedon the device preferences and/or the user preferences, and any otherimage post-processing.

Referring now to FIG. 1-M (as data flows “northward” from FIG. 1-W frommodule 4150), server 4000 may include pixel transmission to user devicemodule 4160, which may be configured to transmit the pixels that havebeen separated out and processed to the specific users that requestedthe image. Pixel transmission to user device module 4160 may handle thetransmission of images to the user devices 5510, 5520, and 5530. In anembodiment, pixel transmission to user device module 4160 may have someor all components in common with user request reception module 4110.

Following the arrow of data flow to the right and upward from module4160 of server 4000, the requested user images arrive at user device5510, user device 5520, and user device 5530, as shown in FIGS. 1-B and1-C. The user devices 5510, 5520, and 5530 may present the receivedimages as previously discussed and/or as further discussed herein.

Referring again to FIG. 1, FIGS. 1-E, 1-O, 1-Y, 1-AH, and 1-AI depict aMUVIA implementation according to an embodiment. In an embodiment,referring now to FIG. 1-E, a user device 5600 may include a targetselection reception module 5610. Target selection reception module 5610may be a component that allows the user to select a “target” from theimage, that is, a point of interest from the image. For example, in theshown example, the MUVIA array is pointed at a football stadium, e.g.,CenturyLink Field. As an example, a user may select one of the footballplayers visible on the field as a “target.” This may be facilitated by atarget presentation module, e.g., target presentation module 5612, whichmay present one or more images (e.g., which may be various versions ofimages from MUVIA, at different resolutions or not up-to-date) fromwhich the user may select the target, e.g., the football player.

In an embodiment, target selection reception module 5610 may include anaudible target selection module 5614 which may be configured to allowthe user to select a target using audible commands, without requiringphysical interaction with a device.

Referring again to FIG. 1, e.g., FIG. 1-E, in an embodiment, user device5600 may include selected target transmission module 5620. Selectedtarget transmission module 5620 may be configured to take the targetselected by the user, and transmit the selected target to the server4000.

Referring now to FIG. 1-O, FIG. 1-O (and FIG. 1-Y to the direct “south”of FIG. 1-O) shows an embodiment of server 4000. For example, in anembodiment, server 4000 may include a selected target reception module4210. In an embodiment, selected target reception module 4210 of server4000 may receive the selected target from the user device 5600. Theselected target data may take various formats, e.g., it may be imagedata, it may be metadata that identifies the selected target, it may besome other designation, e.g., an ID number, a tracking number, or apiece of information, like a license plate or a social security number.The selected target data may be an address or a physical description, orany other instantiation of data that can be used to identify something.

Referring again to FIG. 1-O, in an embodiment, server 4000 may includeselected target identification module 4220, which may be configured totake the target data received by selected target reception module 4210and determine an image that needs to be captured in order to obtain animage that contains the selected target (e.g., in the shown example, thefootball player). In an embodiment, selected target identificationmodule 4220 may use images previously received (or, in an embodiment,current images) from the image sensor array 3200 to determine theparameters of an image that contains the selected target. For example,in an embodiment, lower-resolution images from the image sensor array3200 may be transmitted to server 4000 for determining where the targetis located within the image, and then specific requests for portions ofthe image may be transmitted to the image sensor array 3200, as will bediscussed herein.

In an embodiment, server 4000 may perform processing on the selectedtarget data, and/or on image data that is received, in order to create arequest that is to be transmitted to the image sensor array 3200. Forexample, in the given example, the selected target data is a footballplayer. The server 4000, that is, selected target identification module4220 may perform image recognition on one or more images captured fromthe image sensor array 3200 to determine a “sector” of the entire scenethat contains the selected target. In another embodiment, the selectedtarget identification module 4220 may use other, external sources ofdata to determine where the target is. In yet another embodiment, theselected target data was selected by the user from the scene displayedby the image sensor array 3200, so such processing may not be necessary.

Referring again to FIG. 1-O, in an embodiment, server 4000 may includepixel information selection module 4230, which may select the pixelsneeded to capture the target, and which may determine the size of theimage that should be transmitted from the image sensor array 3200. Thesize of the image may be determined based on a type of target that isselected, one or more parameters (set by the user, by the device, or bythe server, which may or may not be based on the selected target), bythe screen resolution of the device, or by any other algorithm. Pixelinformation selection module 4230 may determine the pixels to becaptured in order to express the target, and may update based on changesin the target's status (e.g., if the target is moving, e.g., in thefootball example, once a play has started and the football player ismoving in a certain direction).

Referring now to FIG. 1-Y, FIG. 1Y includes more of server 4000according to an embodiment. In an embodiment, server 4000 may includepixel information transmission to ISA module 4240. Pixel informationtransmission to ISA module 4240 may transmit the selected pixels to thearray local processing module 3500 associated with image sensor array3200.

Referring now to FIGS. 1-AH and 1-AI, FIG. 1-AH depicts an image sensorarray 3200, which in this example is pointed at a football stadium,e.g., CenturyLink field. Image sensor array 3200 may include one or moreimage sensors that may, in an embodiment, be statically pointed at aparticular object or scene. Image sensor array 3200 may be a singleimage sensor, or more commonly, may be a group of individual imagesensors 3201 that are combined to create a larger field of view. Forexample, in an embodiment, ten megapixel sensors may be used for eachindividual image sensor 3201. With twelve of these sensors, theeffective field of view, loss-less zoom, and so forth may be increasedsubstantially. These numbers are for example only, and any number ofsensors and/or megapixel image sensor capacities may be used.

The use of many individual sensors may create a very large number ofpixels captured for each exposure of the image sensor array 3200. Thus,these pixels are transmitted via a higher bandwidth communication 3505to the array local processing module 3500. In an embodiment, array localprocessing module 3500 is integrated into the image sensor array 3200.In another embodiment, the array local processing module 3500 isseparate from, but directly connected to (e.g., via a USB 3.0 cable) tothe image sensor array 3200. It is noted that “higher bandwidthcommunication 3505” does not require a specific amount of bandwidth, butonly that the bandwidth for this communication is relatively higher thanthe bandwidth communication from the array local processing module 3500to the remote server, which may be, but is not required to be, locatedfurther away temporally.

It is noted that, because of the large number of pixels captured byimage sensor array 3200, mechanical changes to the image sensor array3200 are not generally required, although such mechanical changes arenot excluded from these embodiments. For example, because the array hasa very large field of view, with very high resolution, “pan” and “zoom”functions may be handled optically, rather than by mechanically changingthe focal point of the lenses or by physically pointing the array at adifferent location. This may reduce the complexity required of thedevice, and also may improve the speed at which different views may begenerated by the image sensor array 3200.

Referring again to FIG. 1-AE, the image sensor array 3200 may capture animage that is received by image capturing module 3305. Image capturingmodule 3305 may take the captured image and compare it to a consolidateduser request, e.g., which is provided by a consolidated user requestreception module 3310. Consolidated user request reception module 3310may receive the communication from server 4000 regarding which pixels ofthe image have been requested. Through use of the consolidated userrequest and the captured image, pixel selection module 3320 may selectthe pixels that have been specifically requested by the user, and markthose pixels for transmission back to the server.

After the pixels to be kept are identified, the other pixels that arenot to be kept are removed, e.g., decimated at unused pixel decimationmodule 3330. In an embodiment, these pixels are simply discarded, e.g.,not stored in a long-term memory, that is removed to a digital trash3317. In another embodiment, some or all of these pixels are stored in alocal memory, e.g., local memory 3315. From here, these pixels may betransmitted to various locations at off-peak times, may be kept forimage processing by the array local processing module 3300, or may besubject to other manipulations or processing separate from the userrequests. In an embodiment, unused pixel decimation module 3330 mayinclude or communicate with a lower resolution module 3315, which may,in some embodiments, be used to transmit a lower-resolution version ofmore of the image (e.g., an entire scene, or more of the field of viewsurrounding the target) to the server 4000, so that the server 4000 mayaccurately determine which images are required to capture the targetselected by the user.

Referring again to FIG. 1-AE, the selected pixels then may betransmitted to the server 4000 using selected pixel transmission module3340. Selected pixel transmission module 3340 may include anytransmission equipment necessary, e.g., cellular radio, wirelessadapter, and the like, depending on the format of communication. In anembodiment, only those pixels which have been requested are transmittedto the server via lower-bandwidth communication 3510. Similarly tolower-bandwidth communication 3515, the lower-bandwidth communication3510 does not refer to a specific amount of bandwidth, just that theamount of bandwidth is relatively lower than higher-bandwidthcommunication 3505.

Referring now again to FIG. 1-Y, server 4000 may include a requestedimage reception from ISA module 4250. Requested image reception from ISAmodule 4250 may receive the image data from the array local processingmodule 3500 (e.g., in the arrow coming “north” from FIG. 1-AI. Thatimage, as depicted in FIG. 1-Y, may include the target (e.g., thefootball player), as well as some surrounding area (e.g., the area ofthe field around the football player). The “surrounding area” and thespecifics of what is included/transmitted from the array localprocessing module may be specified by the user (directly or indirectly,e.g., through a set of preferences), or may be determined by the server,e.g., in the pixel information selection module 4230 (shown in FIG.1-O).

Referring again to FIG. 1-Y, server 4000 may also include a requestedimage transmission to user device module 4260. Requested imagetransmission to user device module 4260 may transmit the requested imageto the user device 5600. Requested image transmission to user devicemodule 4260 may include components necessary to communicate with userdevice 5600 and may, in some embodiments, share components with one ormore other modules of server 4000, e.g., a network interface, or awireless antenna.

Referring again to FIG. 1-Y, server 4000 may include a server cachedimage updating module 4270. Server cached image updating module 4270 maytake the images received from the array local processing module 3500(e.g., which may include the image to be sent to the user), and comparethe received images with stored or “cached” images on the server, inorder to determine if the cached images should be updated. This processmay happen frequently or infrequently, depending on embodiments, and maybe continuously ongoing as long as there is a data connection, in someembodiments. In some embodiments, the frequency of the process maydepend on the available bandwidth to the array local processing module3500, e.g., that is, at off-peak times, the frequency may be increased.In an embodiment, server cached image updating module 4270 compares animage received from the array local processing module 3500, and, if theimage has changed, replaces the cached version of the image with thenewer image.

Referring now again to FIG. 1-E, FIG. 1-E shows user device 5600. In anembodiment, user device 5600 includes image containing selected targetreceiving module 5630 that may be configured to receive the image fromserver 4000, e.g., requested image transmission to user device module4260 of server 4000 (e.g., depicted in FIG. 1-Y, with the datatransmission indicated by a rightward-upward arrow passing through FIG.1-Y and FIG. 1-O (to the north) before arriving at FIG. 1-E.

Referring again to FIG. 1-E, FIG. 1-E shows received image presentationmodule 5640, which may display the requested pixels that include theselected target to the user, e.g., by showing them on a screen of thedevice. In an embodiment, the display of the image may be carried outthrough an exemplary interface that allows the user to monitor thetarget, and which also may display information about the target (e.g.,in an embodiment, as shown in the figures, the game statistics for thefootball player also may be shown), which allows a cycle of userrequests and new images to be shown as the user navigates through whatis seen on the MUVIA, e.g., as shown in FIG. 1-A.

Referring again to FIG. 1, FIGS. 1-F, 1-P, 1-Z, and 1-AJ depict a MUVIAimplementation according to an embodiment. This embodiment may becolloquially known as “live street view” in which one or more MUVIAsystems allow for a user to move through an area similarly to the wellknown Google-branded Maps (or Google-Street), except with the camerasworking in real time. For example, in an embodiment, referring now toFIG. 1-F, a user device 5700 may include a target selection inputreception module 5710. Target selection input reception module 5710 maybe a component that allows the user to select a “target” from the image,that is, a point of interest from the image. For example, in the shownexample, the MUVIA may be focused on a city, and the target may be anaddress, a building, a car, or a person in the city. As an example, auser may select a street address as a “target.” This may be facilitatedby a target presentation module, e.g., image selection presentationmodule 5712, which may present one or more images (e.g., which may bevarious versions of images from MUVIA, at different resolutions or notup-to-date) from which the user may select the target, e.g., the streetaddress. In an embodiment, image selection presentation module 5712 mayuse static images that may or may not be sourced by the MUVIA system,and, in another embodiment, image selection presentation module 5712 mayuse current or cached views from the MUVIA system.

In an embodiment, image selection presentation module 5712 may includean audible target selection module 5714 which may be configured to allowthe user to select a target using audible commands, without requiringphysical interaction with a device.

Referring again to FIG. 1, e.g., FIG. 1-F, in an embodiment, user device5700 may include selected target transmission module 5720. Selectedtarget transmission module 5720 may be configured to take the targetselected by the user, and transmit the selected target to the server4000.

Referring now to FIG. 1-P, FIG. 1-P depicts a server 4000 of the MUVIAsystem according to embodiments. In an embodiment, server 4000 mayinclude a selected target reception module 4310. Selected targetreception module 4310 may receive the selected target from the userdevice 5700. In an embodiment, server 4000 may provide all or most ofthe data that facilitates the selection of the target, that is, theimages and the interface, which may be provided, e.g., through a webportal.

Referring again to FIG. 1-P, in an embodiment, server 4000 may include aselected image pre-processing module 4320. Selected image pre-processingmodule 4320 may perform one or more tasks of pre-processing the image,some of which are described herein for exemplary purposes. For example,in an embodiment, selected image pre-processing module 4320 may includea resolution determination module 4322 which may be configured todetermine the resolution for the image in order to show the target (andhere, resolution is merely a stand-in for any facet of the image, e.g.,color depth, size, shadow, pixilation, filter, etc.). In an embodiment,selected image pre-processing module 4320 may include a cached pixelfill-in module 4324. Cached pixel fill-in module 4324 may be configuredto manage which portions of the requested image are recovered from acache, and which are updated, in order to improve performance. Forexample, if a view of a street is requested, certain features of thestreet (e.g., buildings, trees, etc., may not need to be retrieved eachtime, but can be filled in with a cached version, or, in anotherembodiment, can be filled in by an earlier version. A check can be doneto see if a red parked car is still in the same spot as it was in anhour ago; if so, that part of the image may not need to be updated.Using lower resolution/prior images stored in a memory 4215, as well asother image processing techniques, cached pixel fill-in module 4324determines which portions of the image do not need to be retrieved, thusreducing bandwidth load on the connection between the array localprocessing module 3600 and the server 4000.

Referring again to FIG. 1-P, in an embodiment, selected imagepre-processing module 4320 of server 4000 may include a static objectobtaining module 4326, which may operate similarly to cached pixelfill-in module 4324. For example, as in the example shown in FIG. 1-B,static object obtaining module 4326 may obtain prior versions of staticobjects, e.g., buildings, trees, fixtures, landmarks, etc., which maysave bandwidth load on the connection between the array local processingmodule 3600 and the server 4000.

Referring again to FIG. 1-P, in an embodiment, pixel informationtransmission to ISA module 4330 may transmit the request for pixels(e.g., an image, after the pre-processing) to the array local processingmodule 3600 (e.g., as shown in FIGS. 1-Z and 1-AI, with the downwardextending dataflow arrow).

Referring now to FIGS. 1-Z and 1-AJ, in an embodiment, an array localprocessing module 3600, that may be connected by a higher bandwidthconnection to an image sensor array 3200, may be present.

Image sensor array 3200 may include one or more image sensors that may,in an embodiment, be statically pointed at a particular object or scene.Image sensor array 3200 may be a single image sensor, or more commonly,may be a group of individual image sensors 3201 that are combined tocreate a larger field of view. For example, in an embodiment, tenmegapixel sensors may be used for each individual image sensor 3201.With twelve of these sensors, the effective field of view, loss-lesszoom, and so forth may be increased substantially. These numbers are forexample only, and any number of sensors and/or megapixel image sensorcapacities may be used.

The use of many individual sensors may create a very large number ofpixels captured for each exposure of the image sensor array 3200. Thus,these pixels are transmitted via a higher bandwidth communication 3505to the array local processing module 3600. In an embodiment, array localprocessing module 3600 is integrated into the image sensor array 3200.In another embodiment, the array local processing module 3600 isseparate from, but directly connected to (e.g., via a USB 3.0 cable) tothe image sensor array 3200. It is noted that “higher bandwidthcommunication 3505” does not require a specific amount of bandwidth, butonly that the bandwidth for this communication is relatively higher thanthe bandwidth communication from the array local processing module 3600to the remote server, which may be, but is not required to be, locatedfurther away temporally.

It is noted that, because of the large number of pixels captured byimage sensor array 3200, mechanical changes to the image sensor array3200 are not generally required, although such mechanical changes arenot excluded from these embodiments. For example, because the array hasa very large field of view, with very high resolution, “pan” and “zoom”functions may be handled optically, rather than by mechanically changingthe focal point of the lenses or by physically pointing the array at adifferent location. This may reduce the complexity required of thedevice, and also may improve the speed at which different views may begenerated by the image sensor array 3200.

Referring again to FIG. 1-AJ and FIG. 1-Z, the image sensor array 3200may capture an image that is received by image capturing module 3305.Image capturing module 3305 may take the captured image and compare itto a consolidated user request, e.g., which is provided by a requestreception module 3610. Request reception module 3610 may receive thecommunication from server 4000 regarding which pixels of the image havebeen requested. Through use of the consolidated user request and thecaptured image, pixel selection module 3620 may select the pixels thathave been specifically requested by the user, and mark those pixels fortransmission back to the server.

After the pixels to be kept are identified, the other pixels that arenot to be kept are removed, e.g., decimated at unused pixel decimationmodule 3630. In an embodiment, these pixels are simply discarded, e.g.,not stored in a long-term memory, that is removed to a digital trash3617. In another embodiment, some or all of these pixels are stored in alocal memory, e.g., local memory 3615. From here, these pixels may betransmitted to various locations at off-peak times, may be kept forimage processing by the array local processing module 3600, or may besubject to other manipulations or processing separate from the userrequests. In an embodiment, unused pixel decimation module may includeor communicate with a lower resolution module 3514, which may, in someembodiments, be used to transmit a lower-resolution version of more ofthe image (e.g., an entire scene, or more of the field of viewsurrounding the target) to the server 4000, so that the server 4000 mayaccurately determine which images are required to capture the targetselected by the user.

Referring again to FIG. 1-AJ, the selected pixels then may betransmitted to the server 4000 using selected pixel transmission module3640. Selected pixel transmission module 3640 may include anytransmission equipment necessary, e.g., cellular radio, wirelessadapter, and the like, depending on the format of communication. In anembodiment, only those pixels which have been requested are transmittedto the server via lower-bandwidth communication 3510. Similarly tolower-bandwidth communication 3515, the lower-bandwidth communication3510 does not refer to a specific amount of bandwidth, just that theamount of bandwidth is relatively lower than higher-bandwidthcommunication 3505.

It is noted that more pixels than what are specifically requested by theuser may be transmitted, in certain embodiments. For example, the arraylocal processing module 3600 may send pixels that border the user'srequested area, but are outside the user's requested area. In anembodiment, as will be discussed herein, those pixels may be sent at adifferent resolution or using a different kind of compression. Inanother embodiment, the additional pixels may merely be sent the same asthe requested pixels. In still another embodiment, server 4000 mayexpand the user requested areas, so that array local processing module3600 may send only the requested pixels, but the requested pixels covermore area than what the user originally requested. These additionalpixels may be transmitted and “cached” by the server or local device,which may be used to decrease latency times, in a process that will bediscussed more herein.

Referring now again to FIG. 1-P, in an embodiment, server 4000 mayinclude image receiving from ISA module 4340. Image receiving from ISAmodule 4340 may receive the image data from the array local processingmodule 3600 (e.g., in the arrow coming “north” from FIG. 1-AJ via FIG.1-Z). The image may include the pixels that were requested from theimage sensor array 3200. In an embodiment, server 4000 also may includereceived image post-processing module 4350, which may, among otherpost-processing tasks, fill in objects and pixels into the image thatwere determined not to be needed by selected image pre-processing module4320, as previously described. In an embodiment, server 4000 may includereceived image transmission to user device module 4360, which may beconfigured to transmit the requested image to the user device 5700.Requested image transmission to user device module 4360 may includecomponents necessary to communicate with user device 5700 and may, insome embodiments, share components with one or more other modules ofserver 4000, e.g., a network interface, or a wireless antenna.

Referring now again to FIG. 1-F, user device 5700 may include a serverimage reception module 5730. Server image reception module 5730 mayreceive an image sent by the server 4000, and user selection presentingmodule 5240, which may display the requested pixels to the user, e.g.,by showing them on a screen of the device. In an embodiment, the displayof the image may be carried out through the exemplary interface, whichallows a cycle of user requests and new images to be shown as the usernavigates through what is seen on the MUVIA, e.g., as shown in FIG. 1-F.

In an embodiment, as shown in FIGS. 1-F and 1-G, server image receptionmodule 5730 may include an audio stream reception module 5732 and avideo stream reception module 5734. In an embodiment, as discussedthroughout this application, the MUVIA system may capture still images,video, and also sound, as well as other electromagnetic waves and othersignals and data. In an embodiment, the audio signals and the videosignals may be handled together, or they may be handled separately, asseparate streams. Although not every module in the instant diagramseparately shows audio streams and video streams, it is noted here thatall implementations of MUVIA contemplate both audio and video coverage,as well as still image and other data collection.

Referring now to FIG. 1-G, which shows another portion of user device5700, FIG. 1-G may include a display 5755 and a memory 5765, which maybe used to facilitate presentation and/or storage of the receivedimages.

FIGS. 1-H, 1-R, 1-AA, and 1-AB show an embodiment of a MUVIAimplementation. For example, referring now to FIG. 1-H, FIG. 1-H showsan embodiment of a user device 5800. For exemplary purposes, the userdevice 5800 may be an augmented reality device that shows a user lookingdown a “street” at which the user is not actually present, e.g., a“virtual tourism” where the user may use their augmented reality device(e.g., googles, e.g., an Oculus Rift-type headgear device) which may bea wearable computer. It is noted that this embodiment is not limited towearable computers or augmented reality, but as in all of theembodiments described in this disclosure, may be any device. The use ofa wearable augmented/virtual reality device is merely used to forillustrative and exemplary purposes.

In an embodiment, user device 5800 may have a field of view 5810, asshown in FIG. 1-H. The field of view for the user 5810 may beillustrated in FIG. 1-H as follows. The most internal rectangle, shownby the dot hatching, represents the user's “field of view” as they lookat their “virtual world.” The second most internal rectangle, with thestraight line hatching, represents the “nearest” objects to the user,that is, a range where the user is likely to “look” next, by turningtheir head or moving their eyes. In an embodiment, this area of theimage may already be loaded on the device, e.g., through use of aparticular codec, which will be discussed in more detail herein. Theoutermost rectangle, which is the image without hatching, representsfurther outside the user's viewpoint. This area, too, may already beloaded on the device. By loading areas where the user may eventuallylook, the system can reduce latency and make a user's motions, e.g.,movement of head, eyes, and body, appear “natural” to the system.

Referring now to FIGS. 1-AA and 1-AB, these figures show an array localprocessing module 3700 that is connected to an image sensor array 3200(e.g., as shown in FIG. 1-AK, and “viewing” a city as shown in FIG.1-AJ). The image sensor array 3200 may operate as previously describedin this document. In an embodiment, array local processing module 3700may include a captured image receiving module 3710, which may receivethe entire scene captured by the image sensor array 3200, through thehigher-bandwidth communication channel 3505. As described previously inthis application, these pixels may be “cropped” or “decimated” into therelevant portion of the captured image, as described by one or more ofthe user device 5800, the server 4000, and the processing done at thearray local processing module 3700. This process may occur as previouslydescribed. The relevant pixels may be handled by relevant portion ofcaptured image receiving module 3720.

Referring now to FIG. 1-AB, in an embodiment, the relevant pixels forthe image that are processed by relevant portion of captured imagereceiving module 3720 may be encoded using a particular codec atrelevant portion encoding module 3730. In an embodiment, the codec maybe configured to encode the innermost rectangle, e.g., the portion thatrepresents the current user's field of view, e.g., portion 3716, at ahigher resolution, or a different compression, or a combination of both.The codec may be further configured to encode the second rectangle,e.g., with the vertical line hashing, e.g., portion 3714, at a differentresolution and/or a different (e.g., a higher) compression. Similarly,the outermost portion of the image, e.g., the clear portion 3712, mayagain be coded at still another resolution and/or a differentcompression. In an embodiment, the codec itself handles the algorithmfor encoding the image, and as such, in an embodiment, the codec mayinclude information about user device 5800.

As shown in FIG. 1-AB, the encoded portion of the image, includingportions 3716, 3714, and 3712, may be transmitted using encoded relevantportion transmitting module 3740. It is noted that “lower compression,”“more compression,” and “higher compression,” are merely used as oneexample for the kind of processing done by the codec. For example,instead of lower compression, a different sampling algorithm orcompacting algorithm may be used, or a lossier algorithm may beimplemented for various parts of the encoded relevant portion.

Referring now to FIG. 1-R, FIG. 1-R depicts a server 4000 in a MUVIAsystem according to an embodiment. For example, as shown in FIG. 1-R,server 4000 may include, in addition to portions previously described,an encoded image receiving module 4410. Encoded image receiving module4410 may receive the encoded image, encoded as previously described,from encoded relevant portion transmitting module 3740 of array localprocessing module 3700.

Referring again to FIG. 1-R, server 4000 may include an encoded imagetransmission controlling module 4420. Encoded image transmissioncontrolling module 4420 may transmit portions of the image to the userdevice 5800. In an embodiment, at least partially depending on thebandwidth and the particulars of the user device 5800, the server maysend all of the encoded image to the user device 5800, and let the userdevice 5800 decode the portions as needed, or may decode the image andsend portions in piecemeal, or with a different encoding, depending onthe needs of the user device 5800, and the complexity that can behandled by the user device 5800.

Referring again to FIG. 1-H, user device 5800 may include an encodedimage transmission receiving module 5720, which may be configured toreceive the image that is coded in a particular way, e.g., as will bedisclosed in more detail herein. FIG. 1-H also may include an encodedimage processing module 5830 that may handle the processing of theimage, that is, encoding and decoding portions of the image, or otherprocessing necessary to provide the image to the user.

Referring now to FIG. 1-AL, FIG. 1-AL shows an implementation of anApplication Programming Interface (API) for the various MUVIAcomponents. Specifically, image sensor array API 7800 may include, amongother elements, a programming specification for ISA 7810, that mayinclude, for example, libraries, classes, specifications, templates, orother coding elements that generally make up an API, and an accessauthentication module for ISA 7820 that governs API access to thevarious image sensor arrays. The API allows third party developers toaccess the workings of the image sensor array 3200 and the array localprocessing module 3700, so that the third party developers can writeapplications for the array local processing module 3700, as well asdetermine which data captured by the image sensor array 3200 (whichoften may be multiple gigabytes or more of data per second) should bekept or stored or transmitted. In an embodiment, API access to certainfunctions may be limited. For example, a tiered system may allow acertain number of API calls to the MUVIA data per second, per minute,per hour, or per day. In an embodiment, a third party might pay fees orperform a registration that would allow more or less access to the MUVIAdata. In an embodiment, the third party could host their application ona separate web site, and let that web site access the image sensor array3200 and/or the array local processing module 3700 directly.

Referring again to FIG. 1, FIGS. 1-I, 1-J, 1-S, 1-T, 1-AC, 1-AD, 1-AM,and 1-AN, in an embodiment, show a MUVIA implementation that allowsinsertion of advertising (or other context-sensitive material) into theimages displayed to the user.

Referring again to FIG. 1-I, in an embodiment, user device 5900 mayinclude a user selection accepting module 5910. User selection acceptingmodule 5910 may be configured to receive user input about what the userwants to see. For example, as shown in FIG. 1-I, the user selectionaccepting module 5910 may show an image from image sensor array 3200,and the user may “pan” and “zoom” the image using any known interface,including, but not limited to, keyboard, mouse, touch, haptic, augmentedreality interface, voice command, nonverbal motion commands (e.g., aspart of a video game system interface, e.g., the Microsoft Kinect). Itis noted, and as will be discussed in more detail herein, the cameraitself is not “zooming” or “panning,” because the camera does not move.What is happening is that different pixels that are captured by theimage sensor array 3200 are kept by the image sensor array 3200 andtransmitted to the server 4000.

In an embodiment, the “user selection” facilitated by the user selectionaccepting module 5910 may not involve a user at all. For example, in anembodiment, e.g., in a security embodiment, the user selection may behandled completely by machine, and may include “select any portion ofthe image with movement,” or “select any portion of the image in which aperson is recognized,” or “select any portion of the image in which aparticular person, e.g., a person on the FBI most wanted list” isrecognized.

Referring again to FIG. 1-I, in an embodiment, user device 5900 mayinclude a user selection transmitting module 5920. The user selectiontransmitting module 5920 may take the user selection from user selectiontransmitting module 5920, and transmit the selection to the server 4000.The transmission may include some pre-processing, for example, the userdevice 5900 may determine the size and parameters of the image prior tosending the request to the server 4000, or that processing may behandled by the server 4000. Following the thick-line arrow leftward fromuser selection transmitting module 5920 through to FIG. 1-K, thetransmission goes to server 4000, as will be discussed herein. It isnoted that the transmission to the server 4000 may also include dataabout the user device, for example, the screen resolution, the windowsize, the type of device, an identity of the user, a level of servicethe user has paid for (in embodiments in which such services areprioritized by the camera/server), other capabilities of the device,e.g., framerate, and the like.

Referring again to FIG. 1-I, FIG. 1-I also includes a selected imagereceiving module 5930 and a user selection presenting module 5940, whichwill be discussed in more detail herein, with respect to the dataflow ofthis embodiment.

Referring now to FIG. 1-T (graphically represented as “down” and “to theright” of FIG. 1-I), in an embodiment, a server 4000 may include aselected image reception module 4510. In an embodiment, selected imagereception module 4510 of server 4000 may receive the selected targetfrom the user device 5900. The selected target data may take variousformats, e.g., it may be image data, it may be metadata that identifiesthe selected target, it may be some other designation, e.g., an IDnumber, a tracking number, or a piece of information, like a licenseplate or a social security number. The selected target data may be anaddress or a physical description, or any other instantiation of datathat can be used to identify something.

Referring again to FIG. 1-T, in an embodiment, server 4000 may includeselected image pre-processing module 4520. Selected image pre-processingmodule 4520 may perform one or more tasks of pre-processing the image,some of which have been previously described with respect to otherembodiments. In an embodiment, server 4000 also may include pixelinformation transmission to ISA module 4330 configured to transmit theimage request data to the image search array 3200, as has beenpreviously described.

Referring now to FIGS. 1-AD and 1-AN, array local processing module 3700may be connected to an image sensor array 3200 through ahigher-bandwidth communication link 3505, e.g., a USB or PCI port. In anembodiment, image sensor array 3200 may include a request receptionmodule 3710. Request reception module 3710 may receive the request foran image from the server 4000, as previously described. Requestreception module 3710 may transmit the data to a pixel selection module3720, which may receive the pixels captured from image sensor array3200, and select the ones that are to be kept. That is, in anembodiment, through use of the (sometimes consolidated) user requestsand the captured image, pixel selection module 3720 may select thepixels that have been specifically requested by the user, and mark thosepixels for transmission back to the server.

After the pixels to be kept are identified, the other pixels that arenot to be kept are removed, e.g., decimated at unused pixel decimationmodule 3730. In an embodiment, these pixels are simply discarded, e.g.,not stored in a long-term memory, that is removed to a digital trash3717. In another embodiment, some or all of these pixels are stored in alocal memory, e.g., local memory 3715. From here, these pixels may betransmitted to various locations at off-peak times, may be kept forimage processing by the array local processing module 3700, or may besubject to other manipulations or processing separate from the userrequests, as described in previous embodiments. In an embodiment, unusedpixel decimation module 3730 may be used to transmit a lower-resolutionversion of more of the image (e.g., an entire scene, or more of thefield of view surrounding the target) to the server 4000, so that theserver 4000 may accurately determine which images are required tofulfill the request of the user.

Referring again to FIG. 1-AN, the selected pixels then may betransmitted to the server 4000 using selected pixel transmission module3740. Selected pixel transmission module 3740 may include anytransmission equipment necessary, e.g., cellular radio, wirelessadapter, and the like, depending on the format of communication. In anembodiment, only those pixels which have been requested are transmittedto the server via lower-bandwidth communication 3710. Similarly tolower-bandwidth communication 3715, the lower-bandwidth communication3710 does not refer to a specific amount of bandwidth, just that theamount of bandwidth is relatively lower than higher-bandwidthcommunication 3505.

It is noted that more pixels than what are specifically requested by theuser may be transmitted, in certain embodiments. For example, the arraylocal processing module 3700 may send pixels that border the user'srequested area, but are outside the user's requested area. In anembodiment, as will be discussed herein, those pixels may be sent at adifferent resolution or using a different kind of compression. Inanother embodiment, the additional pixels may merely be sent the same asthe requested pixels. In still another embodiment, server 4000 mayexpand the user requested areas, so that array local processing module3700 may send only the requested pixels, but the requested pixels covermore area than what the user originally requested. These additionalpixels may be transmitted and “cached” by the server or local device,which may be used to decrease latency times, in a process that will bediscussed more herein.

Referring now again to FIG. 1-T, in an embodiment, server 4000 mayinclude received image post-processing module 4550. Received imagepost-processing module 4550 may receive the image data from the arraylocal processing module 3700 (e.g., in the arrow coming “north” fromFIG. 1-AN via FIG. 1-AD). The image may include the pixels that wererequested from the image sensor array 3200.

In an embodiment, server 4000 also may include advertisement insertionmodule 4560. Advertisement insertion module 4560 may insert anadvertisement into the received image. The advertisement may be basedone or more of the contents of the image, a characteristic of a user orthe user device, or a setting of the advertisement server component 7700(see, e.g., FIG. 1-AC, as will be discussed in more detail herein). Theadvertisement insertion module 4560 may place the advertisement into theimage using any known image combination techniques, or, in anotherembodiment, the advertisement image may be in a separate layer, overlay,or any other data structure. In an embodiment, advertisement insertionmodule 4560 may include context-based advertisement insertion module4562, which may be configured to add advertisements that are based onthe context of the image. For example, if the image is a live streetview of a department store, the context of the image may showadvertisements related to products sold by that department store, e.g.,clothing, cosmetics, or power tools.

Referring again to FIG. 1-T, server 4000 may include a received imagewith advertisement transmission to user device module 4570 configured totransmit the image. Received image with advertisement transmission touser device module 4570 may include components necessary to communicatewith user device 5900 and may, in some embodiments, share componentswith one or more other modules of server 4000, e.g., a networkinterface, or a wireless antenna.

Referring again to FIG. 1-I, user device 5900 may include a selectedimage receiving module 5930, which may receive the pixels that were sentby the server 4000, and user selection presenting module 5940, which maydisplay the requested pixels to the user, including the advertisement,e.g., by showing them on a screen of the device. In an embodiment, thedisplay of the image may be carried out through the exemplary interface,which allows a cycle of user requests and new images to be shown as theuser navigates through what is seen on the MUVIA, e.g., as shown in FIG.1-I.

Referring now to FIG. 1-AC, FIG. 1-AC shows an advertisement servercomponent 7700 configured to deliver advertisements to the server 4000for insertion into the images prior to delivery to the user. In anembodiment, advertisement server component 7700 may be integrated withserver 4000. In another embodiment, advertisement server component maybe separate from server 4000 and may communicate with server 4000. Inyet another embodiment, rather than interacting with server 4000,advertisement server component 7700 may interact directly with the userdevice 5900, and insert the advertisement into the image after the imagehas been received, or, in another embodiment, cause the user device todisplay the advertisement concurrently with the image (e.g., overlappingor adjacent to). In such embodiments, some of the described modules ofserver 4000 may be incorporated into user device 5900, but thefunctionality of those modules would operate similarly to as previouslydescribed.

Referring again to FIG. 1-AC, in an embodiment, advertisement servercomponent 7700 may include a user data collection module 7705. User datacollection module 7705 may collect data from user device 5900, and usethat data to drive placement of advertisements (e.g., based on a user'sbrowser history, e.g., to sports sites, and the like).

Referring again to FIG. 1-AC, in an embodiment, advertisement servercomponent 7700 may include advertisement database 7715 which includesadvertisements that are ready to be inserted into images. In anembodiment, these advertisements may be created on the fly.

Referring again to FIG. 1-AC, in an embodiment, advertisement servercomponent 7700 may include an advertisement request reception module7710 which receives a request to add an advertisement into the drawing(the receipt of the request is not shown to ease understanding of thedrawings). In an embodiment, advertisement server component 7700 mayinclude advertisement selection module 7720, which may include an imageanalysis module 7722 configured to analyze the image to determine thebest context-based advertisement to place into the image. In anembodiment, that decision may be made by the server 4000, or partly atthe server 4000 and partly at the advertisement server component 7700(e.g., the advertisement server component may have a set ofadvertisements from which a particular one may be chosen). In anembodiment, various third parties may compensate the operators of servercomponent 7700, server 4000, or any other component of the system, inorder to receive preferential treatment.

Referring again to FIG. 1-AC, in an embodiment, advertisement servercomponent 7700 may include a selected advertisement transmission module7730, which may transmit the selected advertisement (or a set ofselected advertisements) to the server 4000. In an embodiment, selectedadvertisement transmission module 7730 may send the complete image withthe advertisement overlaid, e.g., in an implementation in which theadvertisement server component 7700 also handles the placement of theadvertisement. In an embodiment in which advertisement server component7700 is integrated with server 4000, this module may be an internaltransmission module, as may all such transmission/reception modules.

Exemplary Environment 200

Referring now to FIG. 2A, FIG. 2A illustrates an example environment 200in which methods, systems, circuitry, articles of manufacture, andcomputer program products and architecture, in accordance with variousembodiments, may be implemented by at least one server device 230. Imagedevice 220 may include a number of individual sensors that capture data.Although commonly referred to throughout this application as “imagedata,” this is merely shorthand for data that can be collected by thesensors. Other data, including video data, audio data, electromagneticspectrum data (e.g., infrared, ultraviolet, radio, microwave data),thermal data, and the like, may be collected by the sensors.

Referring again to FIG. 2A, in an embodiment, image device 220 mayoperate in an environment 200. Specifically, in an embodiment, imagedevice 220 may capture a scene 215. The scene 215 may be captured by anumber of sensors 243. Sensors 243 may be grouped in an array, which inthis context means they may be grouped in any pattern, on any plane, buthave a fixed position relative to one another. Sensors 243 may capturethe image in parts, which may be stitched back together by processor222. There may be overlap in the images captured by sensors 243 of scene215, which may be removed.

Upon capture of the scene in image device 220, in processes and systemsthat will be described in more detail herein, the requested pixels areselected. Specifically, pixels that have been identified by a remoteuser, by a server, by the local device, by another device, by a programwritten by an outside user with an API, by a component or other hardwareor software in communication with the image device, and the like, aretransmitted to a remote location via a communications network 240. Thepixels that are to be transmitted may be illustrated in FIG. 2A asselected portion 255, however this is a simplified expression meant forillustrative purposes only.

Referring again to FIG. 2A, in an embodiment, server device 230 may beany device or group of devices that is connected to a communicationnetwork. Although in some examples, server device 230 is distant fromimage device 220, that is not required. Server device 230 may be“remote” from image device 220, which may be that they are separatecomponents, but does not necessarily imply a specific distance. Thecommunications network may be a local transmission component, e.g., aPCI bus. Server device 230 may include a request handling module 232that handles requests for images from user devices, e.g., user device250A and 240B. Request handling module 232 also may handle other remotecomputers and/or users that want to take active control of the imagedevice, e.g., through an API, or through more direct control.

Server device 230 also may include an image device management module,which may perform some of the processing to determine which of thecaptured pixels of image device 220 are kept. For example, image devicemanagement module 234 may do some pattern recognition, e.g., torecognize objects of interest in the scene, e.g., a particular footballplayer, as shown in the example of FIG. 2A. In other embodiments, thisprocessing may be handled at the image device 220 or at the user device250. In an embodiment, server device 230 limits a size of the selectedportion by a screen resolution of the requesting user device.

Server device 230 then may transmit the requested portions to the userdevices, e.g., user device 250A and user device 250B. In anotherembodiment, the user device or devices may directly communicate withimage device 220, cutting out server device 230 from the system.

In an embodiment, user device 250A and 250B are shown, however userdevices may be any electronic device or combination of devices, whichmay be located together or spread across multiple devices and/orlocations. Image device 220 may be a server device, or may be auser-level device, e.g., including, but not limited to, a cellularphone, a network phone, a smartphone, a tablet, a music player, awalkie-talkie, a radio, an augmented reality device (e.g., augmentedreality glasses and/or headphones), wearable electronics, e.g., watches,belts, earphones, or “smart” clothing, earphones, headphones,audio/visual equipment, media player, television, projection screen,flat screen, monitor, clock, appliance (e.g., microwave, convectionoven, stove, refrigerator, freezer), a navigation system (e.g., a GlobalPositioning System (“GPS”) system), a medical alert device, a remotecontrol, a peripheral, an electronic safe, an electronic lock, anelectronic security system, a video camera, a personal video recorder, apersonal audio recorder, and the like. Device 220 may include a deviceinterface 243 which may allow the device 220 to output data to theclient in sensory (e.g., visual or any other sense) form, and/or allowthe device 220 to receive data from the client, e.g., through touch,typing, or moving a pointing device (e.g., a mouse). User device 250 mayinclude a viewfinder or a viewport that allows a user to “look” throughthe lens of image device 220, regardless of whether the user device 250is spatially close to the image device 220.

Referring again to FIG. 2A, in various embodiments, the communicationnetwork 240 may include one or more of a local area network (LAN), awide area network (WAN), a metropolitan area network (MAN), a wirelesslocal area network (WLAN), a personal area network (PAN), a WorldwideInteroperability for Microwave Access (WiMAX), public switched telephonenetwork (PTSN), a general packet radio service (GPRS) network, acellular network, and so forth. The communication networks 240 may bewired, wireless, or a combination of wired and wireless networks. It isnoted that “communication network” as it is used in this applicationrefers to one or more communication networks, which may or may notinteract with each other.

Referring now to FIG. 2B, FIG. 2B shows a more detailed version ofserver device 230, according to an embodiment. The server device 230 mayinclude a device memory 245. In an embodiment, device memory 245 mayinclude memory, random access memory (“RAM”), read only memory (“ROM”),flash memory, hard drives, disk-based media, disc-based media, magneticstorage, optical storage, volatile memory, nonvolatile memory, and anycombination thereof. In an embodiment, device memory 245 may beseparated from the device, e.g., available on a different device on anetwork, or over the air. For example, in a networked system, there maybe more than one server device 230 whose device memories 245 may belocated at a central server that may be a few feet away or locatedacross an ocean. In an embodiment, device memory 245 may include of oneor more of one or more mass storage devices, read-only memory (ROM),programmable read-only memory (PROM), erasable programmable read-onlymemory (EPROM), cache memory such as random access memory (RAM), flashmemory, synchronous random access memory (SRAM), dynamic random accessmemory (DRAM), and/or other types of memory devices. In an embodiment,memory 245 may be located at a single network site. In an embodiment,memory 245 may be located at multiple network sites, including sitesthat are distant from each other. In an embodiment, device memory 245may include one or more of cached images 245A and previously retainedimage data 245B, as will be discussed in more detail further herein.

Referring again to FIG. 2B, in an embodiment, server device 230 mayinclude an optional viewport 247, which may be used to view imagescaptured by server device 230. This optional viewport 247 may bephysical (e.g., glass) or electrical (e.g., LCD screen), or may be at adistance from server device 230.

Referring again to FIG. 2B, FIG. 2B shows a more detailed description ofserver device 230. In an embodiment, device 220 may include a processor222. Processor 222 may include one or more microprocessors, CentralProcessing Units (“CPU”), a Graphics Processing Units (“GPU”), PhysicsProcessing Units, Digital Signal Processors, Network Processors,Floating Point Processors, and the like. In an embodiment, processor 222may be a server. In an embodiment, processor 222 may be adistributed-core processor. Although processor 222 is as a singleprocessor that is part of a single device 220, processor 222 may bemultiple processors distributed over one or many devices 220, which mayor may not be configured to operate together.

Processor 222 is illustrated as being configured to execute computerreadable instructions in order to execute one or more operationsdescribed above, and as illustrated in FIG. 10, FIGS. 11A-11G, FIGS.12A-12E, FIGS. 13A-13C, and FIGS. 14A-14E. In an embodiment, processor222 is designed to be configured to operate as processing module 250,which may include one or more of a request for particular image datathat is part of a scene acquiring module 252, a request for particularimage data transmitting to an image sensor array module 254 configuredto transmit the request to the image sensor array that includes morethan one image sensor and that is configured to capture the scene thatis larger than the requested particular image data, a particular imagedata from the image sensor array exclusive receiving module 256configured to transmit the selected particular portion from the scene toa remote location, and a received particular image data transmitting toat least one requestor module 258 configured to de-emphasize pixels fromthe scene that are not part of the selected particular portion of thescene.

Exemplary Environment 300A

Referring now to FIG. 3A, FIG. 3A shows an exemplary embodiment of animage device, e.g., image device 220A operating in an environment 300A.In an embodiment, image device 220A may include an array 310 of imagesensors 312 as shown in FIG. 3. The array of image sensors in this imageis shown in a rectangular grid, however this is merely exemplary to showthat image sensors 312 may be arranged in any format. In an embodiment,each image sensor 312 may capture a portion of scene 315, which portionsare then processed by processor 350. Although processor 350 is shown aslocal to image device 220A, it may be remote to image device 220A, witha sufficiently high-bandwidth connection to receive all of the data fromthe array of image sensors (e.g., multiple USB 3.0 lines). In anembodiment, the selected portions from the scene (e.g., the portionsshown in the shaded box, e.g., selected portion 315), may be transmittedto a remote device 330, which may be a user device or a server device,as previously described. In an embodiment, the pixels that are nottransmitted to remote device 330 may be stored in a local memory 340 ordiscarded.

Exemplary Environment 300B

Referring now to FIG. 4, FIG. 4 shows an exemplary embodiment of animage device, e.g., image device 320B operating in an environment 300B.In an embodiment, image device 320B may include an image sensor array320B, e.g., an array of image sensors, which, in this example, arearranged around a polygon to increase the field of view that can becaptured, that is, they can capture scene 315, illustrated in FIG. 3B asa natural landmark that can be viewed in a virtual tourism setting.Processor 322 receives the scene 315B and selects the pixels from thescene 315B that have been requested by a user, e.g., requested portions317B. Requested portions 317B may include an overlapping area 324B thatis only transmitted once. In an embodiment, the requested portions 317Bmay be transmitted to a remote location via communications network 240.

Exemplary Environment 300C

Referring now to FIG. 3C, FIG. 3C shows an exemplary embodiment of animage device, e.g., image device 320C operating in an environment 300C.In an embodiment, image device 320C may capture a scene, of which a partof the scene, e.g., scene portion 315C, as previously described in otherembodiments (e.g., some parts of image device 320C are omitted forsimplicity of drawing). In an embodiment, e.g., scene portion 315C mayshow a street-level view of a busy road, e.g., for a virtual tourism orvirtual reality simulator. In an embodiment, different portions of thescene portion 315C may be transmitted at different resolutions or atdifferent times. For example, in an embodiment, a central part of thescene portion 315C, e.g., portion 516, which may correspond to what auser's eyes would see, is transmitted at a first resolution, or “full”resolution relative to what the user's device can handle. In anembodiment, an outer border outside portion 316, e.g., portion 314, maybe transmitted at a second resolution, which may be lower, e.g., lowerthan the first resolution. In another embodiment, a further outsideportion, e.g., portion 312, may be discarded, transmitted at a stilllower rate, or transmitted asynchronously.

Exemplary Environment 400A

Referring now to FIG. 4A, FIG. 4A shows an exemplary embodiment of aserver device, e.g., server device 430A. In an embodiment, an imagedevice, e.g., image device 420A may capture a scene 415. Scene 415 maybe stored in local memory 440. The portions of scene 415 that arerequested by the server device 430A may be transmitted (e.g., throughrequested image transfer 465) to requested pixel reception module 432 ofserver device 430A. In an embodiment, the requested pixels transmittedto requested pixel reception module 432 may correspond to images thatwere requested by various users and/or devices (not shown) incommunication with server device 430A.

Referring again to FIG. 4A, in an embodiment, pixels not transmittedfrom local memory 440 of image device 420A may be stored inuntransmitted pixel temporary storage 440B. These untransmitted pixelsmay be stored and transmitted to the server device 430A at a later time,e.g., an off-peak time for requests for images of scene 415. Forexample, in an embodiment, the pixels stored in untransmitted pixeltemporary storage 440B may be transmitted to the unrequested pixelreception module 434 of server device 430A at night, or when other usersare disconnected from the system, or when the available bandwidth totransfer pixels between image device 420A and server device 430A reachesa certain threshold value.

In an embodiment, server device 430A may analyze the pixels received byunrequested pixel reception module 434, for example, to provide arepository of static images from the scene 415 that do not need to betransmitted from the image device 420A each time certain portions ofscene 415 are requested.

Exemplary Environment 400B

Referring now to FIG. 4B, FIG. 4A shows an exemplary embodiment of aserver device, e.g., server device 430B. In an embodiment, an imagedevice, e.g., image device 420B may capture a scene 415B. Scene 415B maybe stored in local memory 440B. In an embodiment, image device 420B maycapture the same scene 415B multiple times. In an embodiment, scene 415Bmay include an unchanged area 416A, which is a portion of the image thathas not changed since the last time the scene 415B was captured by theimage device 420B. In an embodiment, scene 415B also may include achanged area 416B, which may be a portion of the image that has changedsince the last time the scene 415B was captured by the image device420B. Although changed area 416B is illustrated as polygonal andcontiguous in FIG. 4B, this is merely for illustrative purposes, andchanged area 416B may be, in some embodiments, nonpolygonal and/ornoncontiguous.

In an embodiment, image device 420B, upon capturing scene 415B use animage previously stored in local memory 440B to compare the previousimage, e.g., previous image 441B, to the current image, e.g., currentimage 442B, and may determine which areas of the scene 415B have beenchanged. The changed areas may be transmitted to server device 430B,e.g., to changed area reception module 432B. This may occur through achanged area transmission 465, as indicated in FIG. 4B.

Referring again to FIG. 4B, in an embodiment, server device 430Breceives the changed area at changed area reception module 432B. Serverdevice 430B also may include an unchanged area addition module 434B,which adds the unchanged areas that were previously stored in a memoryof server device 430B (not shown) from a previous transmission fromimage device 420B. In an embodiment, server device 430B also may includea complete image transmission module 436B configured to transmit thecompleted image to a user device, e.g., user device 450B, that requestedthe image.

Exemplary Environment 500A

Referring now to FIG. 5A, FIG. 5A shows an exemplary embodiment of aserver device, e.g., server device 530A. In an embodiment, an imagedevice 520A may capture a scene 515 through use of an image sensor array540, as previously described. The image may be temporarily stored in alocal memory 540 (as pictured), or may be partially or wholly stored ina local memory before transmission to a server device 530A. In anembodiment, server device 530A may include an image data receptionmodule 532A. Image data reception module 532A may receive the image fromimage device 520A. In an embodiment, server device 530A may include dataaddition module 534A, which may add additional data to the receivedimage data. In an embodiment, the additional data may be visible orinvisible, e.g., pixel data or metadata, for example. In an embodiment,the additional data may be advertising data. In an embodiment, theadditional data may be context-dependent upon the image data, forexample, if the image data is of a football player, the additional datamay be statistics about that player, or an advertisement for an onlineshop that sells that player's jersey.

In an embodiment, the additional data may be stored in a memory ofserver device 530A (not shown). In another embodiment, the additionaldata may be retrieved from an advertising server or another data server.In an embodiment, the additional data may be tailored to one or morecharacteristics of the user or the user device, e.g., the user may havea setting that labels each player displayed on the screen with thatplayer's last name. Referring again to FIG. 5A, in an embodiment, serverdevice 530A may include a modified data transmission module 536A, whichmay receive the modified data from data addition module 534A, andtransmit the modified data to a user device, e.g., a user device thatrequested the image data, e.g., user device 550A. to the server device430A at a later time, e.g., an off-peak time for requests for images ofscene 415. For example, in an embodiment, the pixels stored inuntransmitted pixel temporary storage 440B may be transmitted to theunrequested pixel reception module 434 of server device 430A at night,or when other users are disconnected from the system, or when theavailable bandwidth to transfer pixels between image device 420A andserver device 430A reaches a certain threshold value.

In an embodiment, server device 430A may analyze the pixels received byunrequested pixel reception module 434, for example, to provide arepository of static images from the scene 415 that do not need to betransmitted from the image device 420A each time certain portions ofscene 415 are requested.

Exemplary Environment 500B

Referring now to FIG. 5B, FIG. 5B shows an exemplary embodiment of aserver device, e.g., server device 530B. In an embodiment, multiple userdevices, e.g., user device 502A, user device 502B, and user device 502C,each may send a request for image data from a scene, e.g., scene 515B.Each user device may send a request to a server device, e.g., serverdevice 530B. Server device 530B may consolidate the requests, which maybe for various resolutions, shapes, sizes, and other features, into asingle combined request 570. Overlapping portions of the request, e.g.,as shown in overlapping area 572, may be combined.

In an embodiment, server device 530B transmits the combined request 570to the image device 520B. In an embodiment, image device 520B uses thecombined request 570 to designate selected pixels 574, which then may betransmitted back to the server device 530B, where the process ofcombining the requests may be reversed, and each user device 502A, 502B,and 502C may receive the requested image. This process will be discussedin more detail further herein.

Exemplary Embodiments of the Various Modules of Portions of Processor250

FIGS. 6-9 illustrate exemplary embodiments of the various modules thatform portions of processor 250. In an embodiment, the modules representhardware, either that is hard-coded, e.g., as in an application-specificintegrated circuit (“ASIC”) or that is physically reconfigured throughgate activation described by computer instructions, e.g., as in acentral processing unit.

Referring now to FIG. 6, FIG. 6 illustrates an exemplary implementationof the request for particular image data that is part of a sceneacquiring module 252. As illustrated in FIG. 6, the request forparticular image data that is part of a scene acquiring module mayinclude one or more sub-logic modules in various alternativeimplementations and embodiments. For example, as shown in FIG. 6, e.g.,FIG. 6A, in an embodiment, module 252 may include one or more of requestfor particular image data that is part of a scene and includes one ormore images acquiring module 602 and request for particular image datathat is part of a scene receiving module 604. In an embodiment, module604 may include request for particular image data that is part of ascene receiving from a client device module 606. In an embodiment,module 606 may include one or more of request for particular image datathat is part of a scene receiving from a client device configured todisplay at least a portion of the scene module 608 and request forparticular image data that is part of a scene receiving from a clientdevice configured to receive a selection of a particular image module612. In an embodiment, module 608 may include request for particularimage data that is part of a scene receiving from a client deviceconfigured to display at least a portion of the scene in a viewfindermodule 610. In an embodiment, module 612 may include one or more ofrequest for particular image data that is part of a scene receiving froma client device configured to receive a scene-based selection of aparticular image module 614 and request for particular image data thatis part of a scene receiving from one or more various devices configuredto receive a scene-based selection of a particular image module 616.

Referring again to FIG. 6, e.g., FIG. 6B, as described above, in anembodiment, module 252 may include one or more of request for particularimage data that is part of a scene that is the image data collected bythe array of more than one image sensor acquiring module 618 and requestfor particular image data that is part of a scene that a representationof the image data collected by the array of more than one image sensoracquiring module 620. In an embodiment, module 620 may include one ormore of request for particular image data that is part of a scene that asampling of the image data collected by the array of more than one imagesensor acquiring module 622, request for particular image data that ispart of a scene that is a subset of the image data collected by thearray of more than one image sensor acquiring module 624, and requestfor particular image data that is part of a scene that is alow-resolution version of the image data collected by the array of morethan one image sensor acquiring module 626.

Referring again to FIG. 6, e.g., FIG. 6C, in an embodiment, module 252may include one or more of request for particular image data that ispart of a scene that is a football game acquiring module 628, requestfor particular image data that is part of a scene that is an area streetview acquiring module 630, request for particular image data that ispart of a scene that is a tourist destination acquiring module 632, andrequest for particular image data that is part of a scene that is insidea home acquiring module 634.

Referring again to FIG. 6, e.g., FIG. 6D, in an embodiment, module 252may include request for particular image data that is an image that is aportion of the scene acquiring module 636. In an embodiment, module 636may include one or more of request for particular image data that is animage that is a particular football player and a scene that is afootball field acquiring module 638 and request for particular imagedata that is an image that is a vehicle license plate and a scene thatis a highway bridge acquiring module 640.

Referring again to FIG. 6, e.g., FIG. 6E, in an embodiment, module 252may include one or more of request for particular image object locatedin the scene acquiring module 642 and particular image data of the scenethat contains the particular image object determining module 644. In anembodiment, module 642 may include one or more of request for particularperson located in the scene acquiring module 646, request for abasketball located in the scene acquiring module 648, request for amotor vehicle located in the scene acquiring module 650, and request fora human object representation located in the scene acquiring module 652.

Referring again to FIG. 6, e.g., FIG. 6F, in an embodiment, module 252may include one or more of first request for first particular image datafrom a first requestor receiving module 662, second request for firstparticular image data from a different second requestor receiving module664, first received request for first particular image data and secondreceived request for second particular image data combining module 666,first request for first particular image data and second request forsecond particular image data receiving module 670, and received firstrequest and received second request combining module 672. In anembodiment, module 666 may include first received request for firstparticular image data and second received request for second particularimage data combining into the request for particular image data module668. In an embodiment, module 672 may include received first request andreceived second request common pixel deduplicating module 674.

Referring again to FIG. 6, e.g., FIG. 6G, in an embodiment, module 252may include one or more of request for particular video data that ispart of a scene acquiring module 676, request for particular audio datathat is part of a scene acquiring module 678, request for particularimage data that is part of a scene receiving from a user device with anaudio interface module 680, and request for particular image data thatis part of a scene receiving from a microphone-equipped user device withan audio interface module 682.

Referring now to FIG. 7, FIG. 7 illustrates an exemplary implementationof request for particular image data transmitting to an image sensorarray module 254. As illustrated in FIG. 7, the request for particularimage data transmitting to an image sensor array module 254 may includeone or more sub-logic modules in various alternative implementations andembodiments. For example, as shown in FIG. 7, e.g., FIG. 7A, in anembodiment, module 254 may include one or more of request for particularimage data transmitting to an image sensor array module configured totransmit the request to the image sensor array that includes more thanone image sensor and that is configured to capture an image that islarger than the requested particular image data 702, request forparticular image data transmitting to an image sensor array moduleconfigured to transmit the request to the image sensor array thatincludes two angled image sensors and that is configured to capture thescene that is larger than the requested particular image data 704,request for particular image data transmitting to an image sensor arraymodule configured to transmit the request to the image sensor array thatincludes more than one image sensor arranged in a grid and that isconfigured to capture the scene that is larger than the requestedparticular image data 706, request for particular image datatransmitting to an image sensor array module configured to transmit therequest to the image sensor array that includes more than one imagesensor arranged in a line and that is configured to capture the scenethat is larger than the requested particular image data 708, and requestfor particular image data transmitting to an image sensor array moduleconfigured to transmit the request to the image sensor array thatincludes more than one nonlinearly arranged stationary image sensor andthat is configured to capture the scene that is larger than therequested particular image data 710.

Referring again to FIG. 7, e.g., FIG. 7B, in an embodiment, module 254may include one or more of request for particular image datatransmitting to an image sensor array that includes an array of staticimage sensors module 712, request for particular image data transmittingto an image sensor array that includes an array of image sensors mountedon a movable platform module 716, request for particular image datatransmitting to an image sensor array module configured to transmit therequest to the image sensor array that includes more than one imagesensor and that is configured to capture the scene that represents moredata than the requested particular image data 718, and request forparticular image data transmitting to an image sensor array moduleconfigured to transmit the request to the image sensor array thatincludes more than one image sensor and that is configured to capturethe scene that represents a greater field of view than the requestedparticular image data 724. In an embodiment, module 712 may includerequest for particular image data transmitting to an image sensor arraythat includes an array of static image sensors that have fixed focallength and fixed field of view module 714. In an embodiment, module 718may include one or more of request for particular image datatransmitting to an image sensor array module configured to transmit therequest to the image sensor array that includes more than one imagesensor and that is configured to capture the scene that represents tentimes as much data as the requested particular image data 720 andrequest for particular image data transmitting to an image sensor arraymodule configured to transmit the request to the image sensor array thatincludes more than one image sensor and that is configured to capturethe scene that represents more than one hundred times as much data asthe requested particular image data 722.

Referring again to FIG. 7, e.g., FIG. 7C, in an embodiment, module 254may include one or more of request for particular image data modifyingmodule 726 and modified request for particular image data transmittingto an image sensor array module 728. In an embodiment, module 726 mayinclude designated image data removing from request for particular imagedata module 730. In an embodiment, module 730 may include designatedimage data removing from request for particular image data based onpreviously stored image data module 732. In an embodiment, module 732may include one or more of designated image data removing from requestfor particular image data based on previously stored image dataretrieved from the image sensor array module 734 and designated imagedata removing from request for particular image data based on previouslystored image data that is an earlier-in-time version of the designatedimage data module 736. In an embodiment, module 736 may includedesignated image data removing from request for particular image databased on previously stored image data that is an earlier-in-time versionof the designated image data that is a static object module 738.

Referring again to FIG. 7, e.g., FIG. 7D, in an embodiment, module 254may include module 726 and module 728, as previously discussed. In anembodiment, module 726 may include one or more of designated image dataremoving from request for particular image data based on pixel datainterpolation/extrapolation module 740, portion of the request forparticular image data that was previously stored in memory identifyingmodule 744, and identified portion of the request for the particularimage data removing module 746. In an embodiment, module 740 may includedesignated image data corresponding to one or more static image objectsremoving from request for particular image data based on pixel datainterpolation/extrapolation module 742. In an embodiment, module 744 mayinclude one or more of portion of the request for the particular imagedata that was previously captured by the image sensor array identifyingmodule 748 and portion of the request for the particular image data thatincludes at least one static image object that was previously capturedby the image sensor array identifying module 750. In an embodiment,module 750 may include portion of the request for the particular imagedata that includes at least one static image object of a rockoutcropping that was previously captured by the image sensor arrayidentifying module 752.

Referring again to FIG. 7, e.g., FIG. 7E, in an embodiment, module 254may include one or more of size of request for particular image datadetermining module 754 and determined-size request for particular imagedata transmitting to the image sensor array module 756. In anembodiment, module 754 may include one or more of size of request forparticular image determining at least partially based on user deviceproperty module 758, size of request for particular image determining atleast partially based on user device access level module 762, size ofrequest for particular image determining at least partially based onavailable bandwidth module 764, size of request for particular imagedetermining at least partially based on device usage time module 766,and size of request for particular image determining at least partiallybased on device available bandwidth module 768. In an embodiment, module758 may include size of request for particular image determining atleast partially based on user device resolution module 760.

Referring now to FIG. 8, FIG. 8 illustrates an exemplary implementationof particular image data from the image sensor array exclusive receivingmodule 256. As illustrated in FIG. 8A, the particular image data fromthe image sensor array exclusive receiving module 256 may include one ormore sub-logic modules in various alternative implementations andembodiments. For example, as shown in FIG. 8, e.g., FIG. 8A, in anembodiment, module 256 may include one or more of particular image datafrom the image sensor array in which other image data is discardedreceiving module 802, particular image data from the image sensor arrayin which other image data is stored at the image sensor array receivingmodule 804, and particular image data from the image sensor arrayexclusive near-real-time receiving module 806.

Referring again to FIG. 8, e.g., FIG. 8B, in an embodiment, module 256may include one or more of particular image data from the image sensorarray exclusive near-real-time receiving module 808 and data from thescene other than the particular image data retrieving at a later timemodule 810. In an embodiment, module 810 may include one or more of datafrom the scene other than the particular image data retrieving at a timeof available bandwidth module 812, data from the scene other than theparticular image data retrieving at an off-peak usage time of the imagesensor array module 814, data from the scene other than the particularimage data retrieving at a time when no particular image data requestsare present at the image sensor array module 816, and data from thescene other than the particular image data retrieving at a time ofavailable image sensor array capacity module 818.

Referring again to FIG. 8, e.g., FIG. 8C, in an embodiment, module 256may include one or more of particular image data that includes audiodata from the image sensor array exclusive receiving module 820 andparticular image data that was determined to contain a particularrequested image object from the image sensor array exclusive receivingmodule 822. In an embodiment, module 822 may include particular imagedata that was determined to contain a particular requested image objectby the image sensor array exclusive receiving module 824.

Referring now to FIG. 9, FIG. 9 illustrates an exemplary implementationof received particular image data transmitting to at least one requestormodule 258. As illustrated in FIG. 9A, the received particular imagedata transmitting to at least one requestor module 258 may include oneor more sub-logic modules in various alternative implementations andembodiments. For example, as shown in FIG. 9, e.g., FIG. 9A, in anembodiment, module 258 may include one or more of received particularimage data transmitting to at least one user device requestor module902, separation of the received particular data into set of one or morerequested images executing module 906, and received particular imagedata transmitting to at least one user device that requested image datathat is part of the received particular image data module 912. In anembodiment, module 902 may include received particular image datatransmitting to at least one user device that requested at least aportion of the received particular data requestor module 904. In anembodiment, module 906 may include separation of the received particulardata into a first requested image and a second requested image executingmodule 910.

Referring again to FIG. 9, e.g., FIG. 9B, in an embodiment, module 258may include one or more of first portion of received particular imagedata transmitting to the first requestor module 914, second portion ofreceived particular image data transmitting to a second requestor module916, and received particular image data unaltered transmitting to atleast one requestor module 926. In an embodiment, module 914 may includefirst portion of received particular image data transmitting to thefirst requestor that requested the first portion module 918. In anembodiment, module 918 may include portion of received particular imagedata that includes a particular football player transmitting to atelevision device that requested the football player from a footballgame module 920. In an embodiment, module 916 may include second portionof received particular image data transmitting to the second requestorthat requested the second portion module 922. In an embodiment, module922 may include portion that contains a view of a motor vehicletransmitting to the second requestor that is a tablet device thatrequested the view of the motor vehicle module 924.

Referring again to FIG. 9, e.g., FIG. 9C, in an embodiment, module 258may include one or more of supplemental data addition to at least aportion of the received particular image data to generate transmissionimage data facilitating module 928 and generated transmission image datatransmitting to at least one requestor module 930. In an embodiment,module 928 may include one or more of advertisement data addition to atleast a portion of the received particular image data to generatetransmission image data facilitating module 932 and related visual dataaddition to at least a portion of the received particular image data togenerate transmission image data facilitating module 938. In anembodiment, module 932 may include context-based advertisement dataaddition to at least a portion of the received particular image data togenerate transmission image data facilitating module 934. In anembodiment, module 934 may include animal rights donation fundadvertisement data addition to at least a portion of the receivedparticular image data that includes a jungle tiger at an oasis togenerate transmission image data facilitating module 936. In anembodiment, module 938 may include related fantasy football statisticaldata addition to at least a portion of the received particular imagedata of a quarterback data to generate transmission image datafacilitating module 940.

Referring again to FIG. 9, e.g., FIG. 9D, in an embodiment, module 258may include one or more of portion of received particular image datamodification to generate transmission image data facilitating module 942and generated transmission image data transmitting to at least onerequestor module 944. In an embodiment, module 942 may include one ormore of portion of received particular image data image manipulationmodification to generate transmission image data facilitating module 946and portion of received particular image data redaction to generatetransmission image data facilitating module 952. In an embodiment,module 946 may include one or more of portion of received particularimage data contrast balancing modification to generate transmissionimage data facilitating module 948 and portion of received particularimage data color modification balancing to generate transmission imagedata facilitating module 950. In an embodiment, module 952 may includeportion of received particular image data redaction to generatetransmission image data based on a security clearance level of therequestor facilitating module 954. In an embodiment, module 954 mayinclude portion of received satellite image data that includes a tankredaction to generate transmission image data based on a securityclearance level of the requestor facilitating module 956.

Referring again to FIG. 9, e.g., FIG. 9D, in an embodiment, module 258may include one or more of lower-resolution version of receivedparticular image data transmitting to at least one requestor module 958and full-resolution version of received particular image datatransmitting to at least one requestor module 960.

In some implementations described herein, logic and similarimplementations may include software or other control structures.Electronic circuitry, for example, may have one or more paths ofelectrical current constructed and arranged to implement variousfunctions as described herein. In some implementations, one or moremedia may be configured to bear a device-detectable implementation whensuch media hold or transmit device detectable instructions operable toperform as described herein. In some variants, for example,implementations may include an update or modification of existingsoftware or firmware, or of gate arrays or programmable hardware, suchas by performing a reception of or a transmission of one or moreinstructions in relation to one or more operations described herein.Alternatively or additionally, in some variants, an implementation mayinclude special-purpose hardware, software, firmware components, and/orgeneral-purpose components executing or otherwise invokingspecial-purpose components. Specifications or other implementations maybe transmitted by one or more instances of tangible transmission mediaas described herein, optionally by packet transmission or otherwise bypassing through distributed media at various times.

Following are a series of flowcharts depicting implementations. For easeof understanding, the flowcharts are organized such that the initialflowcharts present implementations via an example implementation andthereafter the following flowcharts present alternate implementationsand/or expansions of the initial flowchart(s) as either sub-componentoperations or additional component operations building on one or moreearlier-presented flowcharts. Those having skill in the art willappreciate that the style of presentation utilized herein (e.g.,beginning with a presentation of a flowchart(s) presenting an exampleimplementation and thereafter providing additions to and/or furtherdetails in subsequent flowcharts) generally allows for a rapid and easyunderstanding of the various process implementations. In addition, thoseskilled in the art will further appreciate that the style ofpresentation used herein also lends itself well to modular and/orobject-oriented program design paradigms.

Exemplary Operational Implementation of Processor 250 and ExemplaryVariants

Further, in FIG. 10 and in the figures to follow thereafter, variousoperations may be depicted in a box-within-a-box manner. Such depictionsmay indicate that an operation in an internal box may comprise anoptional example embodiment of the operational step illustrated in oneor more external boxes. However, it should be understood that internalbox operations may be viewed as independent operations separate from anyassociated external boxes and may be performed in any sequence withrespect to all other illustrated operations, or may be performedconcurrently. Still further, these operations illustrated in FIG. 10 aswell as the other operations to be described herein may be performed byat least one of a machine, an article of manufacture, or a compositionof matter.

Those having skill in the art will recognize that the state of the arthas progressed to the point where there is little distinction leftbetween hardware, software, and/or firmware implementations of aspectsof systems; the use of hardware, software, and/or firmware is generally(but not always, in that in certain contexts the choice between hardwareand software can become significant) a design choice representing costvs. efficiency tradeoffs. Those having skill in the art will appreciatethat there are various vehicles by which processes and/or systems and/orother technologies described herein can be effected (e.g., hardware,software, and/or firmware), and that the preferred vehicle will varywith the context in which the processes and/or systems and/or othertechnologies are deployed. For example, if an implementer determinesthat speed and accuracy are paramount, the implementer may opt for amainly hardware and/or firmware vehicle; alternatively, if flexibilityis paramount, the implementer may opt for a mainly softwareimplementation; or, yet again alternatively, the implementer may opt forsome combination of hardware, software, and/or firmware. Hence, thereare several possible vehicles by which the processes and/or devicesand/or other technologies described herein may be effected, none ofwhich is inherently superior to the other in that any vehicle to beutilized is a choice dependent upon the context in which the vehiclewill be deployed and the specific concerns (e.g., speed, flexibility, orpredictability) of the implementer, any of which may vary. Those skilledin the art will recognize that optical aspects of implementations willtypically employ optically-oriented hardware, software, and or firmware.

Throughout this application, examples and lists are given, withparentheses, the abbreviation “e.g.,” or both. Unless explicitlyotherwise stated, these examples and lists are merely exemplary and arenon-exhaustive. In most cases, it would be prohibitive to list everyexample and every combination. Thus, smaller, illustrative lists andexamples are used, with focus on imparting understanding of the claimterms rather than limiting the scope of such terms.

Referring now to FIG. 10, FIG. 10 shows operation 1000, e.g., an exampleoperation of message processing device 230 operating in an environment200. In an embodiment, operation 1000 may include operation 1002depicting acquiring a request for particular image data that is part ofa scene. For example, FIG. 6, e.g., FIG. 6B, shows request forparticular image data that is part of a scene acquiring module 252acquiring (e.g., receiving, e.g., from a device that requested an image,that is any device or set of devices capable of displaying, storing,analyzing, or operating upon an image, e.g., television, computer,laptop, smartphone, etc., e.g., or from an entity that requested animage, e.g., a person, an automated monitoring system, an artificialintelligence, an intelligence amplification (e.g., a computer designedto watch for persons appearing on video or still shots), or otherwiseobtaining (e.g., acquiring includes receiving, retrieving, creating,generating, generating a portion of, receiving a location of, receivingaccess instructions for, receiving a password for, etc.) a request(e.g., data, in any format that indicates a computationally-basedrequest for data, e.g., image data, from any source, whetherproperly-formed or not, and which may come from a communications networkor port, or an input/output port, or from a human or other entity, orany device) for particular image data (e.g., a set of image data, e.g.,graphical representations of things, e.g., that are composed of pixelsor other electronic data, or that are captured by an image sensor, e.g.,a CCM or a CMOS sensor), or other data, such as audio data and otherdata on the electromagnetic spectrum, e.g., infrared data, microwavedata, etc.) that is part of a scene (e.g., a particular area, and/ordata (including graphical data, audio data, and factual/derived data)that makes up the particular area, which may in some embodiments be allof the data, pixel data or otherwise, that is captured by the imagesensor array or portions of the image sensor array).

capturing (e.g., collecting data, that includes visual data, e.g., pixeldata, sound data, electromagnetic data, nonvisible spectrum data, andthe like) that includes one or more images (e.g., graphicalrepresentations of things, e.g., that are composed of pixels or otherelectronic data, or that are captured by an image sensor, e.g., a CCM ora CMOS sensor), through use of an array (e.g., any grouping configuredto work together in unison, regardless of arrangement, symmetry, orappearance) of more than one image sensor (e.g., a device, component, orcollection of components configured to collect light, sound, or otherelectromagnetic spectrum data, and/or to convert the collected intodigital data, or perform at least a portion of the foregoing actions).

Referring again to FIG. 10, operation 1000 may include operation 1004depicting transmitting the request for the particular image data to animage sensor array that includes more than one image sensor and that isconfigured to capture the scene that is larger than the requestedparticular image data. For example, FIG. 2, e.g., FIG. 2B, shows requestfor particular image data transmitting to an image sensor array module254 transmitting the request (e.g., data, in any format that indicates acomputationally-based request for data, e.g., image data, from anysource, whether properly-formed or not, and which may come from acommunications network or port, or an input/output port, or from a humanor other entity, or any device) for particular image data (e.g., a setof image data, e.g., graphical representations of things, e.g., that arecomposed of pixels or other electronic data, or that are captured by animage sensor, e.g., a CCM or a CMOS sensor), or other data, such asaudio data and other data on the electromagnetic spectrum, e.g.,infrared data, microwave data, etc., and which may be some subset of theentire scene that includes some pixel data, whether pre-orpost-processing, which may or may not include data from multiple sensorsof the array of more than one image sensor) to an image sensor arraythat includes more than one image sensor (e.g., a device, component, orcollection of components configured to collect light, sound, or otherelectromagnetic spectrum data, and/or to convert the collected intodigital data, or perform at least a portion of the foregoing actions)and that is configured to capture the scene (e.g., the data, e.g., imagedata or otherwise (e.g., sound, electromagnetic, captured by the arrayof more than one image sensor, which may be or may be capable of beingcombined or stitched together, at any stage of processing, pre, orpost)), captured by the array of more than one image sensor, combined orstitched together, at any stage of processing, pre, or post), that islarger (e.g., some objectively measurable feature has a higher orgreater value, e.g., size, resolution, color, color depth, pixel datagranularity, number of colors, hue, saturation, alpha value, shading)than the requested particular image data.

Referring again to FIG. 10, operation 1000 may include operation 1006depicting receiving only the particular image data from the image sensorarray. For example, FIG. 2 e.g., FIG. 2B shows particular image datafrom the image sensor array exclusive receiving module 256 receivingonly (e.g., not transmitting the parts of the scene that are not part ofthe selected particular portion) the particular image data (e.g., thedesignated pixel data that was transmitted from the image sensor array)from the image sensor array (e.g., a set of one or more image sensorsthat are grouped together, whether spatially grouped or linkedelectronically or through a network, in any arrangement orconfiguration, whether contiguous or noncontiguous, and whether in apattern or not, and which image sensors may or may not be uniformthroughout the array).

Referring again to FIG. 10, operation 1000 may include operation 1008depicting transmitting the received particular image data to at leastone requestor. For example, FIG. 2, e.g., FIG. 2B, shows receivedparticular image data transmitting to at least one requestor module 258transmitting the received particular image data (e.g., at leastpartially, but not solely, the designated pixel data that wastransmitted from the image sensor array, which data may be modified,added to, subtracted from, or changed, as will be discussed herein) toat least one requestor (the particular image data may be separated intorequested data and sent to the requesting entity that requested thedata, whether that requesting entity is a device, person, artificialintelligence, or part of a computer routine or system, or the like).

FIGS. 11A-11G depict various implementations of operation 1002,depicting acquiring a request for particular image data that is part ofa scene according to embodiments. Referring now to FIG. 11A, operation1002 may include operation 1102 depicting acquiring the request forparticular image data of the scene that includes one or more images. Forexample, FIG. 6, e.g., FIG. 6A shows request for particular image datathat is part of a scene and includes one or more images acquiring module602 acquiring (e.g., receiving, e.g., from a device that requested animage, that is any device or set of devices capable of displaying,storing, analyzing, or operating upon an image, e.g., television,computer, laptop, smartphone, etc., e.g., or from an entity thatrequested an image, e.g., a person, an automated monitoring system, anartificial intelligence, an intelligence amplification (e.g., a computerdesigned to watch for persons appearing on video or still shots), arequest (e.g., data, in any format that requests an image) forparticular image data of the scene that includes one or more images(e.g., the scene, e.g., a street corner, includes one or more images,e.g., images of a wristwatch worn by a person crossing the streetcorner, images of the building on the street corner, etc.).

Referring again to FIG. 11A, operation 1002 may include operation 1104depicting receiving the request for particular image data of the scene.For example, FIG. 6, e.g., FIG. 6A, shows request for particular imagedata that is part of a scene receiving module 604 receiving (e.g., froma device, e.g., a user's personal laptop device) the request forparticular image data (e.g., a particular player from a game) of thescene (e.g., the portions of the game that are captured by the imagesensor array).

Referring again to FIG. 11A, operation 1104 may include operation 1106depicting receiving the request for particular image data of the scenefrom a user device. For example, FIG. 6, e.g., FIG. 6A, shows requestfor particular image data that is part of a scene receiving from aclient device module 606 receiving (e.g., receiving a call from an APIthat is accessing a remote server that sends commands to the imagesensor array) the request for particular image data (e.g., a still shotof an area outside a building where any movement has been detected,e.g., a security camera shot) of the scene from a user device (e.g., theAPI that was downloaded by an independent user is running on that user'sdevice).

Referring again to FIG. 11A, operation 1106 may include operation 1108depicting receiving the request for particular image data of the scenefrom a user device that is configured to display at least a portion ofthe scene. For example, FIG. 6, e.g., FIG. 6A, shows request forparticular image data that is part of a scene receiving from a clientdevice configured to display at least a portion of the scene module 608receiving the request for particular image data (e.g., image data of aparticular animal) of the scene (e.g., image data that includes thesounds and video from an animal oasis) from a user device (e.g., a smarttelevision) that is configured to display at least a portion of thescene (e.g., the data captured by an image sensor array of the animaloasis).

Referring again to FIG. 11A, operation 1108 may include operation 1110depicting receiving the request for particular image data of the scenefrom a user device that is configured to display at least a portion ofthe scene in a viewfinder. For example, FIG. 6, e.g., FIG. 6A, showsrequest for particular image data that is part of a scene receiving froma client device configured to display at least a portion of the scene ina viewfinder module 610 receiving the request for particular image data(e.g., images of St. Peter's Basilica in Rome, Italy) of the scene(e.g., image data captured by the image sensor array of the Vatican)from a user device (e.g., a smartphone device) that is configured todisplay at least a portion of the scene (e.g., the Basilica, to bedisplayed on the screen as part of a virtual tourism app running on thesmartphone) in a viewfinder (e.g., a screen or set of screens, whetherreal or virtual, that can display and/or process image data). It isnoted that a viewfinder may be remote from where the image is captured.

Referring again to FIG. 11A, operation 1106 may include operation 1112depicting receiving the request for particular image data of the scenefrom the user device that is configured to receive a selection of aparticular image. For example, FIG. 6, e.g., FIG. 6A, shows request forparticular image data that is part of a scene receiving from a clientdevice configured to receive a selection of a particular image module612 receiving the request for particular image data of the scene fromthe user device that is configured to receive a selection of aparticular image (e.g., the user device, e.g., a computer device,receives an audible command from a user regarding which portion of thescene the user wants to see (e.g., which may involve showing a “demo”version of the scene, e.g., a lower-resolution older version of thescene, for example), and the device receives this selection and thensends the request for the particular image data to the server device.

Referring again to FIG. 11A, operation 1112 may include operation 1114depicting receiving the request for particular image data of the scenefrom the user device that is configured to receive the selection of theparticular image, said selection based on a view of the scene. Forexample, FIG. 6, e.g., FIG. 6A, shows request for particular image datathat is part of a scene receiving from a client device configured toreceive a scene-based selection of a particular image module 614receiving the request for particular image data of the scene from theuser device that is configured to receive the selection of theparticular image, said selection based on a view of the scene.

Referring again to FIG. 11A, operation 1112 may include operation 1116depicting receiving the request for particular image data of the scenefrom the user receiving the request for particular image data of thescene from the user device that is configured to receive the selectionof the particular image, wherein the user device is one or more of asmartphone, television, computer screen, tablet, camera, appliance, andaugmented reality device. For example, FIG. 6, e.g., FIG. 6A, showsrequest for particular image data that is part of a scene receiving fromone or more various devices configured to receive a scene-basedselection of a particular image module 616 receiving the request forparticular image data of the scene from the user receiving the requestfor particular image data of the scene from the user device that isconfigured to receive the selection of the particular image, wherein theuser device is one or more of a smartphone, television, computer screen,tablet, camera, appliance, and augmented reality device

Referring now to FIG. 11B, operation 1002 may include operation 1118depicting acquiring the request for particular image data of the scene,wherein the scene is the image data collected by the array of more thanone image sensor. For example, FIG. 6, e.g., FIG. 6B, shows request forparticular image data that is part of a scene that is the image datacollected by the array of more than one image sensor acquiring module618 acquiring the request for particular image data of the scene (e.g.,a live street view of a corner in New York City near Madison SquareGarden), wherein the scene is the image data (e.g., video and audiodata) collected by the array of more than one image sensor (e.g., a setof twenty-five ten-megapixel CMOS sensors arranged at an angle toprovide a full view).

Referring again to FIG. 11B, operation 1002 may include operation 1120depicting acquiring the request for particular image data of the scene,wherein the scene is a representation of the image data collected by thearray of more than one image sensor. For example, FIG. 6, e.g., FIG. 6B,shows request for particular image data that is part of a scene that arepresentation of the image data collected by the array of more than oneimage sensor acquiring module 620 acquiring the request for particularimage data (e.g., an image of a particular street vendor) of the scene(e.g., a city street in Alexandra, Va.), wherein the scene is arepresentation (e.g., metadata, e.g., data about the image data, e.g., asampling, a subset, a description, a retrieval location) of the imagedata (e.g., the pixel data) collected by the array of more than oneimage sensor (e.g., one thousand CMOS sensors of two megapixels each,mounted on a UAV).

Referring again to FIG. 11B, operation 1120 may include operation 1122depicting acquiring the request for particular image data of the scene,wherein the scene is a sampling of the image data collected by the arrayof more than one image sensor. For example, FIG. 6, e.g., FIG. 6B, showsrequest for particular image data that is part of a scene that asampling of the image data collected by the array of more than one imagesensor acquiring module 622 acquiring the request for particular imagedata of the scene, wherein the scene is a sampling (e.g., a subset,selected randomly or through a pattern) of the image data (e.g., animage of a checkout line at a discount store) collected (e.g., gathered,read, stored) by the array of more than one image sensor (e.g., an arrayof two thirty megapixel sensors angled towards each other).

Referring again to FIG. 11B, operation 1120 may include operation 1124depicting acquiring the request for particular image data of the scene,wherein the scene is a subset of the image data collected by the arrayof more than one image sensor. For example, FIG. 6, e.g., FIG. 6B, showsrequest for particular image data that is part of a scene that is asubset of the image data collected by the array of more than one imagesensor acquiring module 624 acquiring the request for particular imagedata (e.g., a particular object inside of a house, e.g., a refrigerator)of the scene (e.g., an interior of a house), wherein the scene is asubset of the image data (e.g., a half of, or a sampling of the whole,or a selected area of, or only the contrast data, etc.,) collected bythe array of more than one image sensor (e.g., a 10×10 grid ofthree-megapixel image sensors).

Referring again to FIG. 11B, operation 1120 may include operation 1126depicting acquiring the request for particular image data of the scene,wherein the scene is a low-resolution version of the image datacollected by the array of more than one image sensor. For example, FIG.6, e.g., FIG. 6B, shows request for particular image data that is partof a scene that is a low-resolution version of the image data collectedby the array of more than one image sensor acquiring module 626acquiring the request for particular image data (e.g., an image of aparticular car crossing a bridge) of the scene (e.g., a highway bridge),wherein the scene is a low-resolution (e.g., “low” here meaning “lessthan a possible resolution given the equipment that captured the image”)version of the image data collected by the array of more than one imagesensor.

Referring now to FIG. 11C, operation 1002 may include operation 1128depicting acquiring the request for particular image data of a scenethat is a football game. For example, FIG. 6, e.g., FIG. 6C, showsrequest for particular image data that is part of a scene that is afootball game acquiring module 628 acquiring the request for particularimage data of a scene that is a football game.

Referring again to FIG. 11C, operation 1002 may include operation 1130depicting acquiring the request for particular image data of a scenethat is a street view of an area. For example, FIG. 6, e.g., FIG. 6C,shows request for particular image data that is part of a scene that isan area street view acquiring module 630 acquiring the request forparticular image data that is a street view (e.g., a live orshort-delayed view) of an area (e.g., a street corner, a garden oasis, amountaintop, an airport, etc.).

Referring again to FIG. 11C, operation 1002 may include operation 1132depicting acquiring the request for particular image data of a scenethat is a tourist destination. For example, FIG. 6, e.g., FIG. 6C, showsrequest for particular image data that is part of a scene that is atourist destination acquiring module 632 acquiring the request forparticular image data of a scene that is a tourist destination (e.g.,the great pyramids of Giza).

Referring again to FIG. 11C, operation 1002 may include operation 1134depicting acquiring the request for particular image data of a scenethat is an inside of a home. For example, FIG. 6, e.g., FIG. 6C, showsrequest for particular image data that is part of a scene that is insidea home acquiring module 634 acquiring the request for particular imagedata of a scene that is inside of a home (e.g., inside a kitchen).

Referring now to FIG. 11D, operation 1002 may include operation 1136depicting acquiring the request for particular image data of the scene,wherein the particular image data is an image that is a portion of thescene. For example, FIG. 6, e.g., FIG. 6D, shows request for particularimage data that is an image that is a portion of the scene acquiringmodule 636 acquiring the request for particular image data (e.g., animage of a tiger in a wildlife preserve), wherein the particular imagedata (e.g., an image of a tiger) that is a portion of the scene (e.g.,image data of the wildlife preserve).

Referring again to FIG. 11D, operation 1136 may include operation 1138depicting acquiring the request for particular image data of the scene,wherein the particular image data includes image data of a particularfootball player and the scene is a football field. For example, FIG. 6,e.g., FIG. 6D, shows request for particular image data that is an imagethat is a particular football player and a scene that is a footballfield acquiring module 638 acquiring the request for particular imagedata of the scene, wherein the particular image data includes image dataof a particular football player and the scene is a football field.

Referring again to FIG. 11D, operation 1136 may include operation 1140depicting acquiring the request for particular image data of the scene,wherein the particular image data includes image data of a license plateof a vehicle, and the scene is an image representation of a highwaybridge. For example, FIG. 6, e.g., FIG. 6D, shows request for particularimage data that is an image that is a vehicle license plate and a scenethat is a highway bridge acquiring module 640 acquiring the request forparticular image data of the scene, wherein the particular image dataincludes image data of a license plate of a vehicle, and the scene is ahighway bridge (e.g., an image of the highway bridge).

Referring now to FIG. 11E, operation 1002 may include operation 1142depicting acquiring a request for a particular image object located inthe scene. For example, FIG. 6, e.g., FIG. 6E, shows request forparticular image object located in the scene acquiring module 642acquiring a request for a particular image object (e.g., a particulartype of bird) located in the scene (e.g., a bird sanctuary).

Referring again to FIG. 11E, operation 1002 may include operation 1144,which may appear in conjunction with operation 1142, operation 1144depicting determining the particular image data of the scene thatcontains the particular image object. For example, FIG. 6, e.g., FIG.6E, shows particular image data of the scene that contains theparticular image object determining module 644 determining theparticular image data (e.g., a 1920×1080 image that contains theparticular type of bird) of the scene (e.g., the image of the birdsanctuary) that contains the particular image object (e.g., theparticular type of bird).

Referring again to FIG. 11E, operation 1142 may include operation 1146depicting acquiring a request for a particular person located in thescene. For example, FIG. 6, e.g., FIG. 6E, shows request for particularperson located in the scene acquiring module 646 acquiring a request fora particular person (e.g., a person dressed a certain way, or loiteringoutside of a warehouse, or a particular celebrity or athlete, or abusiness tracking a specific worker) located in the scene (e.g., animage data).

Referring again to FIG. 11E, operation 1142 may include operation 1148depicting acquiring a request for a basketball located in the scene thatis a basketball arena. For example, FIG. 6, e.g., FIG. 6E, shows requestfor a basketball located in the scene acquiring module 648 acquiring arequest for a basketball (e.g., the image data corresponding to abasketball) located in the scene that is a basketball arena.

Referring again to FIG. 11E, operation 1142 may include operation 1150depicting acquiring a request for a motor vehicle located in the scene.For example, FIG. 6, e.g., FIG. 6E, shows request for a motor vehiclelocated in the scene acquiring module 650 acquiring a request for amotor vehicle located in the scene.

Referring again to FIG. 11E, operation 1142 may include operation 1152depicting acquiring a request for any human object representationslocated in the scene. For example, FIG. 6, e.g., FIG. 6E, shows requestfor a human object representation located in the scene acquiring module652 acquiring a request for any human object representations (e.g., whenany image data corresponding to a human walks by, e.g., for a securitycamera application, or an application that takes an action when a personapproaches, e.g., an automated terminal) located in the scene.

Referring again to FIG. 11E, operation 1142 may include operation 1153depicting determining the particular image data of the scene thatcontains the particular image object through application of automatedpattern recognition to scene image data. For example, FIG. 6, e.g., FIG.6E, shows particular image data of the scene that contains theparticular image object determining through automated patternrecognition application to scene data module 653 determining theparticular image data of the scene (e.g., a tennis match) that containsthe particular image object (e.g., a tennis player) through applicationof automated pattern recognition (e.g., recognizing human images throughmachine recognition, e.g., shape-based classification, head-shoulderdetection, motion-based detection, and component-based detection) toscene image data.

Referring again to FIG. 11E, operation 1144 may include operation 1154depicting determining the particular image data of the scene thatcontains the particular image object through identification of theparticular image object in previous scene data that is image data of thescene from at least one previous moment in time. For example, FIG. 6,e.g., FIG. 6E, shows particular image data of the scene that containsthe particular image object determining through object identification inprevious scene data module 654 determining the particular image data ofthe scene that contains the particular image object throughidentification of the particular image object in previous scene datathat is image data of the scene from at least one previous moment intime.

Referring again to FIG. 11E, operation 1144 may include operation 1156depicting determining the particular image data of the scene thatcontains the particular image object through identification of theparticular image object in cached scene data. For example, FIG. 6, e.g.,FIG. 6E, shows particular image data of the scene that contains theparticular image object determining through object identification incached previous scene data module 656

Referring again to FIG. 11E, operation 1156 may include operation 1158depicting determining the particular image data of the scene thatcontains the particular image object through identification of theparticular image object in cached scene data that was previouslytransmitted from the image sensor array that includes more than oneimage sensor. For example, FIG. 6, e.g., FIG. 6E, shows particular imagedata of the scene that contains the particular image object determiningthrough object identification in cached previous scene data previouslytransmitted from the image sensor array module 658 determining theparticular image data of the scene that contains the particular imageobject (e.g., a particular landmark, or animal at a watering hole)through identification of the particular image object (e.g., a lion at awatering hole) in cached scene data that was previously transmitted fromthe image sensor array (e.g., a set of twenty five image sensors) thatincludes more than one image sensor (e.g., a three megapixel CMOSsensor).

Referring again to FIG. 11E, operation 1156 may include operation 1160depicting determining the particular image data of the scene thatcontains the particular image object through identification of theparticular image object in cached scene data that was previouslytransmitted from the image sensor array that includes more than oneimage sensor at a time when bandwidth was available for a connection tothe image sensor array that includes more than one image sensor. Forexample, FIG. 6, e.g., FIG. 6E, shows particular image data of the scenethat contains the particular image object determining through objectidentification in cached previous scene data previously transmitted fromthe image sensor array at a particular time module 660 determining theparticular image data of the scene that contains the particular imageobject (e.g., a specific item in a shopping cart that doesn't match acash-register generated list of what was purchased by the personwheeling the cart) through identification of the particular image object(e.g., the specific item, e.g., a toaster oven) in cached scene data(e.g., data that is stored in the server that was from a previous pointin time, whether one-millionth of a second previously or yearspreviously, although in the example the cached scene data is from aprevious frame, e.g., less than one second prior) that was previouslytransmitted from the image sensor array that includes more than oneimage sensor at a time when bandwidth was available for connection tothe image sensor array that includes more than one image sensor.

Referring now to FIG. 11F, operation 1002 may include operation 1162depicting receiving a first request for first particular image data fromthe scene from a first requestor. For example, FIG. 6, e.g., FIG. 6F,shows first request for first particular image data from a firstrequestor receiving module 662 receiving a first request (e.g., arequest for a 1920×180 “HD” view) for first particular image data (e.g.,a first animal, e.g., a tiger, at a watering hole scene) from the scene(e.g., a watering hole) from a first requestor (e.g., a family watchingthe watering hole from an internet-connected television).

Referring again to FIG. 11F, operation 1002 may include operation 1164,which may appear in conjunction with operation 1162, operation 1164depicting receiving a second request for second particular image datafrom the scene from a second requestor that is different than the firstrequestor. For example, FIG. 6, e.g., FIG. 6F, shows second request forfirst particular image data from a different second requestor receivingmodule receiving a second request (e.g., a 640×480 view for asmartphone) for second particular image data (e.g., a second animal,e.g., a pelican) from the scene (e.g., a watering hole) from a secondrequestor (e.g., a person watching a stream of the watering hole ontheir smartphone).

Referring again to FIG. 11F, operation 1002 may include operation 1166depicting combining a received first request for first particular imagedata from the scene and a received second request for second particularimage data from the scene. For example, FIG. 6, e.g., FIG. 6F, showsfirst received request for first particular image data and secondreceived request for second particular image data combining module 666combining a received first request for first particular image data(e.g., a request to watch a running back of a football team) from thescene and a received second request for second particular image data(e.g., a request to watch a quarterback of the same football team) fromthe scene (e.g., a football game).

Referring again to FIG. 11F, operation 1166 may include operation 1168depicting combining the received first request for first particularimage data from the scene and the received second request for secondparticular image data from the scene into the request for particularimage data that consolidates overlapping requested image data. Forexample, FIG. 6, e.g., FIG. 6F, shows first received request for firstparticular image data and second received request for second particularimage data combining into the request for particular image data module668 combining the received first request for first particular image data(e.g., request from device 502A, as shown in FIG. 5B) from the scene andthe received second request for second particular image data (e.g., therequest from device 502B, as shown in FIG. 5B) from the scene into therequest for particular image data that consolidates overlappingrequested image data (e.g., the selected pixels 574, as shown in FIG.5B).

Referring again to FIG. 11F, operation 1166 may include operation 1170depicting receiving a first request for first particular image data fromthe scene and a second request for second particular image data from thescene. For example, FIG. 6, e.g., FIG. 6F, shows first request for firstparticular image data and second request for second particular imagedata receiving module 670 receiving a first request for first particularimage data (e.g., image data of a particular street corner from a streetview) from the scene (e.g., a live street view of DoG street inAlexandria, Va.) and a second request for second particular image data(e.g., image data of the opposite corner of the live street view) fromthe scene (e.g., the live street view of DoG street in Alexandria, Va.).

Referring again to FIG. 11F, operation 1002 may include operation 1172,which may appear in conjunction with operation 1170, operation 1172depicting combining the received first request and the received secondrequest into the request for particular image data. For example, FIG. 6,e.g., FIG. 6F, shows received first request and received second requestcombining module 672 combining the received first request (e.g., a1920×1080 request for a virtual tourism view of the Sphinx) and thereceived second request (e.g., a 410×210 request for a virtual tourismview of an overlapping, but different part of the Sphinx) into therequest for particular image data (e.g., the request that will be sentto the image sensor array that regards which pixels will be kept).

Referring again to FIG. 11F, operation 1172 may include operation 1174depicting removing common pixel data between the received first requestand the received second request. For example, FIG. 6, e.g., FIG. 6F,shows received first request and received second request common pixeldeduplicating module 674 removing (e.g., deleting, marking, flagging,erasing, storing in a different format, storing in a different place,coding/compressing using a different algorithm, changing but notnecessarily destroying, destroying, allowing to be written over by newdata, etc.) common pixel data (e.g., pixel data that was part of morethan one request) between the received first request (e.g., a request toview the left fielder of the Washington Nationals from a baseball game)and the received second request (e.g., a request to view the rightfielder of the Washington Nationals from a baseball game).

Referring now to FIG. 11G, operation 1002 may include operation 1176depicting acquiring the request for particular image data that is partof the scene, wherein the particular image data includes video data. Forexample, FIG. 6, e.g., FIG. 6G, shows request for particular video datathat is part of a scene acquiring module 676 acquiring the request forparticular image data that is part of the scene, wherein the particularimage data includes video data (e.g., streaming data, e.g., as in a livestreet view of a corner near the Verizon Center in Washington, D.C.).

Referring again to FIG. 11G, operation 1002 may include operation 1178depicting acquiring the request for particular image data that is partof the scene, wherein the particular image data includes audio data. Forexample, FIG. 6, e.g., FIG. 6G, shows request for particular audio datathat is part of a scene acquiring module 678 acquiring the request forparticular image data that is part of the scene, wherein the particularimage data includes audio data (e.g., data of the sounds at an oasis, orof people in the image that are speaking).

Referring again to FIG. 11G, operation 1002 may include operation 1180depicting acquiring the request for particular image data that is partof the scene from a user device that receives the request for particularimage data through an audio interface. For example, FIG. 6, e.g., FIG.6G, shows request for particular image data that is part of a scenereceiving from a user device with an audio interface module 680acquiring the request for particular image data (e.g., to watch aparticular person on the field at a football game, e.g., thequarterback) that is part of the scene (e.g., the scene of a footballstadium during a game) from a user device (e.g., an internet-connectedtelevision) that receives the request for particular image data throughan audio interface (e.g., the person speaks to an interface built intothe television to instruct the television regarding which player tofollow)

Referring again to FIG. 11G, operation 1002 may include operation 1182depicting acquiring the request for particular image data that is partof the scene from a user device that has a microphone that receives aspoken request for particular image data from the user. For example,FIG. 6, e.g., FIG. 6G, shows request for particular image data that ispart of a scene receiving from a microphone-equipped user device with anaudio interface module 682 acquiring the request for particular imagedata (e.g., an image of a cheetah at a jungle oasis) that is part of thescene (e.g., a jungle oasis) from a user device that has a microphone(e.g., a smartphone device) that receives a spoken request (e.g., “zoomin on the cheetah”) for particular image data (e.g., an image of acheetah at a jungle oasis) for particular image data (e.g., an image ofa cheetah at a jungle oasis) from the user (e.g., the person operatingthe smartphone device that wants to zoom in on the cheetah).

FIGS. 12A-12E depict various implementations of operation 1004,depicting transmitting the request for the particular image data to animage sensor array that includes more than one image sensor and that isconfigured to capture the scene that is larger than the requestedparticular image data, according to embodiments. Referring now to FIG.12A, operation 1004 may include operation 1202 depicting transmittingthe request for the particular image data of the scene to the imagesensor array that includes more than one image sensor and that isconfigured to capture an image that is larger than the requested imagedata. For example, FIG. 7, e.g., FIG. 7A, shows request for particularimage data transmitting to an image sensor array that includes more thanone image sensor and to capture a larger image module 702 transmittingthe request for the particular image data of the scene to the imagesensor array (e.g., an array of twelve sensors of ten megapixels each)that includes more than one image sensor and that is configured tocapture an image that is larger than the requested image data (e.g., therequested image data is 1920×1080 (e.g., roughly 2 million pixels), andthe captured area is 12,000,000 pixels, minus overlap).

Referring again to FIG. 12A, operation 1004 may include operation 1204depicting transmitting the request for the particular image data of thescene to the image sensor array that includes two image sensors arrangedside by side and angled toward each other and that is configured tocapture an image that is larger than the requested image data. Forexample, FIG. 7, e.g., FIG. 7A, shows request for particular image datatransmitting to an image sensor array module configured to transmit therequest to the image sensor array that includes two angled image sensorsand that is configured to capture the scene that is larger than therequested particular image data 704 transmitting the request for theparticular image data of the scene (e.g., a chemistry lab) to the imagesensor array that includes two image sensors arranged side by side andangled toward each other and that is configured to capture an image thatis larger than the requested image data (e.g., the requested image is azoomed-out view of the lab that can be expressed in 1.7 million pixels,but the cameras capture 10.5 million pixels).

Referring again to FIG. 12A, operation 1004 may include operation 1206depicting transmitting the request for the particular image data of thescene to the image sensor array that includes the array of image sensorsarranged in a grid and that is configured to capture an image that islarger than the requested image data. For example, FIG. 7, e.g., FIG.7A, shows request for particular image data transmitting to an imagesensor array module configured to transmit the request to the imagesensor array that includes more than one image sensor arranged in a gridand that is configured to capture the scene that is larger than therequested particular image data 706 transmitting the request for theparticular image data of the scene to the image sensor array thatincludes the array of image sensors arranged in a grid and that isconfigured to capture an image that is larger than the requested imagedata (e.g., the image data requested is of a smaller area (e.g., thearea around a football player) than the image (e.g., the entire footballfield)).

Referring again to FIG. 12A, operation 1004 may include operation 1208depicting transmitting the request for the particular image data of thescene to the image sensor array that includes the array of image sensorsarranged in a line such that a field of view is greater than 120 degreesand that is configured to capture an image that is larger than therequested image data. For example, FIG. 7, e.g., FIG. 7A, shows requestfor particular image data transmitting to an image sensor array moduleconfigured to transmit the request to the image sensor array thatincludes more than one image sensor arranged in a line and that isconfigured to capture the scene that is larger than the requestedparticular image data 708 transmitting the request for the particularimage data of the scene to the image sensor array that includes thearray of image sensors arranged in a line such that a field of view isgreater than 120 degrees and that is configured to capture an image(e.g., an image of a highway) that is larger than the requested imagedata (e.g., an image of one or more of the cars on the highway).

Referring again to FIG. 12A, operation 1004 may include operation 1210depicting transmitting the request for the particular image data of thescene to the image sensor array that includes a grouping of nonlinearly,nonsequentially arranged stationary image sensors and that is configuredto capture an image that is larger than the requested image data. Forexample, FIG. 7, e.g., FIG. 7A, shows request for particular image datatransmitting to an image sensor array module configured to transmit therequest to the image sensor array that includes more than onenonlinearly arranged stationary image sensor and that is configured tocapture the scene that is larger than the requested particular imagedata 710 transmitting the request for the particular image data of thescene to the image sensor array that includes a grouping of nonlinearly,nonsequentially arranged stationary image sensors (e.g., five-megapixelCCD sensors) and that is configured to capture an image that is largerthan the requested image data.

Referring now to FIG. 12B, operation 1004 may include operation 1212depicting transmitting the request for the particular image data of thescene to the image sensor array that includes the array of static imagesensors and that is configured to capture an image that is larger thanthe requested image data. For example, FIG. 7, e.g., FIG. 7B, showsrequest for particular image data transmitting to an image sensor arraythat includes an array of static image sensors module 712 transmittingthe request for the particular image data of the scene to the imagesensor array that includes the array of static image sensors and that isconfigured to capture an image that is larger than the requested imagedata.

Referring again to FIG. 12B, operation 1212 may include operation 1214depicting transmitting the request for the particular image data of thescene to the image sensor array that includes the array of image sensorsthat have a fixed focal length and a fixed field of view and that isconfigured to capture an image that is larger than the requested imagedata. For example, FIG. 7, e.g., FIG. 7B, shows request for particularimage data transmitting to an image sensor array that includes an arrayof static image sensors that have fixed focal length and fixed field ofview module 714 transmitting the request for the particular image data(e.g., an image of a black bear) of the scene (e.g., a mountain wateringhole) to the image sensor array that includes the array of image sensors(e.g., twenty-five megapixel CMOS sensors) that have a fixed focallength and a fixed field of view and that is configured to capture animage that is larger than the requested image data (e.g., the imagerequested is ultra high resolution but represents a smaller area thanwhat is captured in the scene).

Referring again to FIG. 12B, operation 1004 may include operation 1216depicting transmitting the request for the particular image data of thescene to the image sensor array that includes the array of image sensorsmounted on a movable platform and that is configured to capture thescene that is larger than the requested image data. For example, FIG. 7,e.g., FIG. 7B, shows request for particular image data transmitting toan image sensor array that includes an array of image sensors mounted ona movable platform module 716 transmitting the request for theparticular image data of the scene to the image sensor array thatincludes the array of image sensors mounted on a movable platform (e.g.,a movable dish, or a UAV) and that is configured to capture the scene(e.g., the scene is a wide angle view of a city) that is larger than therequested image data (e.g., one building or street corner of the city).

Referring again to FIG. 12B, operation 1004 may include operation 1218depicting transmitting the request for the particular image data of thescene to the image sensor array that includes more than one image sensorand that is configured to capture the scene that represents more imagedata than the requested particular image data. For example, FIG. 7,e.g., FIG. 7B, shows request for particular image data transmitting toan image sensor array module configured to transmit the request to theimage sensor array that includes more than one image sensor and that isconfigured to capture the scene that represents more data than therequested particular image data 718 transmitting the request for theparticular image data of the scene to the image sensor array thatincludes more than one image sensor and that is configured to capturethe scene that represents more image data than the requested particulardata.

Referring again to FIG. 12B, operation 1218 may include operation 1220depicting transmitting the request for the particular image data of thescene to the image sensor array that includes more than one image sensorand that is configured to capture the scene that represents more thanten times as much image data as the requested particular image data. Forexample, FIG. 7, e.g., FIG. 7B, shows request for particular image datatransmitting to an image sensor array module configured to transmit therequest to the image sensor array that includes more than one imagesensor and that is configured to capture the scene that represents tentimes as much data as the requested particular image data 720transmitting the request for the particular image data of the scene tothe image sensor array that includes more than one image sensor and thatis configured to capture the scene that represents more than ten times(e.g., twenty million pixels) as much image data as the requestedparticular image data (e.g., 1.8 million pixels).

Referring again to FIG. 12B, operation 1218 may include operation 1222depicting transmitting the request for the particular image data of thescene to the image sensor array that includes more than one image sensorand that is configured to capture the scene that represents more thanone hundred times as much image data as the requested particular imagedata. For example, FIG. 7, e.g., FIG. 7B, shows request for particularimage data transmitting to an image sensor array module configured totransmit the request to the image sensor array that includes more thanone image sensor and that is configured to capture the scene thatrepresents more than one hundred times as much data as the requestedparticular image data 722 transmitting the request for the particularimage data (e.g., a 1920×1080 image of a red truck crossing a bridge) ofthe scene (e.g., a highway bridge) to the image sensor array (e.g., aset of one hundred sensors) that includes more than one image sensor(e.g., twenty sensors each of two megapixel, four megapixel, sixmegapixel, eight megapixel, and ten megapixel) and that is configured tocapture the scene that represents more than one hundred times (e.g., 600million pixels vs. the requested two million pixels) as much image dataas the requested particular image data.

Referring again to FIG. 12B, operation 1004 may include operation 1224depicting transmitting the request for the particular image data to theimage sensor array that is configured to capture the scene thatrepresents a greater field of view than the requested particular imagedata. For example, FIG. 7, e.g., FIG. 7B, shows request for particularimage data transmitting to an image sensor array module configured totransmit the request to the image sensor array that includes more thanone image sensor and that is configured to capture the scene thatrepresents a greater field of view than the requested particular imagedata 724 transmitting the request for the particular image data (e.g.,an image of a bakery shop on a corner) to the image sensor array that isconfigured to capture the scene (e.g., a live street view of a busystreet corner) that represents a greater field of view (e.g., the entirecorner) than the requested image data (e.g., just the bakery).

Referring now to FIG. 12C, operation 1004 may include operation 1226modifying the request for the particular image data. For example, FIG.7, e.g., FIG. 7C, shows request for particular image data modifyingmodule 726 modifying (e.g., altering, changing, adding to, subtractingfrom, deleting, supplementing, changing the form of, changing anattribute of, etc.) the request for the particular image data (e.g., arequest for an image of a baseball player).

Referring again to FIG. 12C, operation 1004 may include operation 1228,which may appear in conjunction with operation 1226, operation 1228depicting transmitting the modified request for the particular imagedata to the image sensor array that includes more than one image sensorand that is configured to capture the scene that is larger than therequested particular image data. For example, FIG. 7, e.g., FIG. 7C,shows modified request for particular image data transmitting to animage sensor array module 728 transmitting the modified request (e.g.,the request increases the area around the baseball player that wasrequested) for the particular image data to the image sensor array thatincludes more than one image sensor and that is configured to capturethe scene (e.g., a baseball game at a baseball stadium) that is largerthan the requested particular image data.

Referring again to FIG. 12C, operation 1226 may include operation 1230depicting removing designated image data from the request for theparticular image data. For example, FIG. 7, e.g., FIG. 7C, showsdesignated image data removing from request for particular image datamodule 730 removing designated image data (e.g., image data of a staticobject that has already been captured and stored in memory, e.g., abuilding from a live street view, or a car that has not moved since thelast request) from the request for the particular image data (e.g., arequest to see a part of the live street view).

Referring again to FIG. 12C, operation 1230 may include operation 1232depicting removing designated image data from the request for theparticular image data based on previously stored image data. Forexample, FIG. 7, e.g., FIG. 7C, shows designated image data removingfrom request for particular image data based on previously stored imagedata module 732 removing designated image data (e.g., image data of astatic object that has already been captured and stored in memory, e.g.,a building from a live street view, or a car that has not moved sincethe last request) from the request for the particular image data (e.g.,a request to see a part of the live street view) based on previouslystored image data (e.g., the most previously requested image has the carin it already, and so it will not be checked again for another sixtyframes of captured image data, for example).

Referring again to FIG. 12C, operation 1232 may include operation 1234depicting removing designated image data from the request for theparticular image data based on previously stored image data retrievedfrom the image sensor array. For example, FIG. 7, e.g., FIG. 7C, showsdesignated image data removing from request for particular image databased on previously stored image data retrieved from the image sensorarray module 734 removing designated image data from the request for theparticular image data based on previously stored image data retrievedfrom the image sensor array (e.g., the image sensor array sent the olderversion of the data that included a static object, e.g., a part of abridge when the scene is a highway bridge, and so the request for thescene that includes part of the bridge, the part of the bridge that isstatic is removed).

Referring again to FIG. 12C, operation 1232 may include operation 1236depicting removing designated image data from the request for theparticular image data based on previously stored image data that is anearlier-in-time version of the designated image data. For example, FIG.7, e.g., FIG. 7C, shows designated image data removing from request forparticular image data based on previously stored image data that is anearlier-in-time version of the designated image data module 736 removingdesignated image data (e.g., portions of a stadium) from the request forthe particular image data (e.g., a request to view a player inside astadium for a game) based on previously stored image data (e.g., imagedata of the stadium) that is an earlier-in-time version of thedesignated image data (e.g., the image data of the stadium from one hourprevious, or from one frame previous).

Referring again to FIG. 12C, operation 1236 may include operation 1238depicting removing image data of one or more static objects from therequest for the particular image data that is a view of a street, basedon previously stored image data of the one or more static objects froman earlier-in-time version captured by the image sensor array. Forexample, FIG. 7, e.g., FIG. 7C, shows designated image data removingfrom request for particular image data based on previously stored imagedata that is an earlier-in-time version of the designated image datathat is a static object module 738 removing image data of one or morestatic objects from the request for the particular image data that is aview of a street, based on previously stored image data of the one ormore static objects from an earlier-in-time version captured by theimage sensor array.

Referring now to FIG. 12D, operation 1226 may include operation 1240depicting removing portions of the request for the particular image datathrough pixel interpolation or extrapolation of portions of the requestfor the particular image data. For example, FIG. 7, e.g., FIG. 7D, showsdesignated image data removing from request for particular image databased on pixel data interpolation/extrapolation module 740 removingportions of the request for the particular image data (e.g., portions ofa uniform building) through pixel interpolation (e.g., filling in themiddle of the building based on extrapolation of a known pattern of thebuilding) of portions of the request for the particular image data(e.g., a request for a live street view that includes a building).

Referring again to FIG. 12D, operation 1240 may include operation 1242depicting removing one or more static objects from the request for theparticular image data through pixel interpolation of the portions of therequest for the particular image data. For example, FIG. 7, e.g., FIG.7D, shows designated image data corresponding to one or more staticimage objects removing from request for particular image data based onpixel data interpolation/extrapolation module 742 removing one or morestatic objects (e.g., a brick of a pyramid) through pixel interpolation(e.g., filling in the middle of the pyramid based on extrapolation of aknown pattern of the pyramid) of portions of the request for theparticular image data (e.g., a request for a live street view thatincludes a building).

Referring again to FIG. 12D, operation 1226 may include operation 1244depicting identifying at least one portion of the request for theparticular image data that is already stored in a memory. For example,FIG. 7, e.g., FIG. 7D, shows portion of the request for particular imagedata that was previously stored in memory identifying module 744identifying at least one portion of the request for the particular imagedata (e.g., a request for a virtual tourism exhibit of which a part hasbeen cached in memory from a previous access) that is already stored ina memory (e.g., a memory of the server device, e.g., memory 245).

Referring again to FIG. 12D, operation 1226 may include operation 1246,which may appear in conjunction with operation 1244, operation 1246depicting removing the identified portion of the request for theparticular image data. For example, FIG. 7, e.g., FIG. 7D, showsidentified portion of the request for the particular image data removingmodule 746 removing the identified portion of the request for theparticular image data (e.g., removing the part of the request thatrequests the image data that is already stored in a memory of theserver).

Referring again to FIG. 12D, operation 1226 may include operation 1248depicting identifying at least one portion of the request for particularimage data that was previously captured by the image sensor array. Forexample, FIG. 7, e.g., FIG. 7D, shows portion of the request for theparticular image data that was previously captured by the image sensorarray identifying module 748 identifying at least one portion of therequest for particular image data that was previously captured by theimage sensor array (e.g., an array of twenty-five two megapixel CMOSsensors).

Referring again to FIG. 12D, operation 1226 may include operation 1250depicting identifying one or more static objects of the request forparticular image data that was previously captured by the image sensorarray. For example, FIG. 7, e.g., FIG. 7D, shows portion of the requestfor the particular image data that includes at least one static imageobject that was previously captured by the image sensor arrayidentifying module 750 identifying one or more static objects (e.g.,buildings, roads, trees, etc.) of the request for particular image data(e.g., image data of a part of a rural town) that was previouslycaptured by the image sensor array.

Referring again to FIG. 12D, operation 1250 may include operation 1252depicting identifying one or more natural rock outcroppings of therequest for particular image data that was previously captured by theimage sensor array. For example, FIG. 7, e.g., FIG. 7D, shows portion ofthe request for the particular image data that includes at least onestatic image object of a rock outcropping that was previously capturedby the image sensor array identifying module 752 identifying one or morenatural rock outcroppings of the request for particular image data thatwas previously captured by the image sensor array (e.g., an array oftwenty-five two megapixel CMOS sensors).

Referring now to FIG. 12E, operation 1004 may include operation 1254depicting determining a size of the request for the particular imagedata. For example, FIG. 7, e.g., FIG. 7E, shows size of request forparticular image data determining module 754 determining a size (e.g., anumber of pixels, or a transmission speed, or a number of frames persecond) of the request for the particular image data (e.g., data of alion at a jungle oasis).

Referring again to FIG. 12E, operation 1004 may include operation 1256,which may appear in conjunction with operation 1254, operation 1256depicting transmitting the request for the particular image data forwhich the size has been determined to the image sensor array that isconfigured to capture the scene. For example, FIG. 7, e.g., FIG. 7E,shows determined-size request for particular image data transmitting tothe image sensor array module 756 transmitting the request for theparticular image data for which the size has been determined to theimage sensor array that is configured to capture the scene (e.g., ascene of an interior of a home).

Referring again to FIG. 12E, operation 1254 may include operation 1258depicting determining the size of the request for the particular imagedata at least partially based on a property of a user device thatrequested at least a portion of the particular image data. For example,FIG. 7, e.g., FIG. 7E, shows size of request for particular imagedetermining at least partially based on user device property module 758determining the size (e.g., the horizontal and vertical resolutions,e.g., 1920×1080) of the request for the particular image data at leastpartially based on a property of a user device that requested at least aportion of the particular image data.

Referring again to FIG. 12E, operation 1258 may include operation 1260depicting determining the size of the request for the particular imagedata at least partially based on a resolution of the user device thatrequested the particular image data. For example, FIG. 7, e.g., FIG. 7E,shows size of request for particular image determining at leastpartially based on user device resolution module 760 determining thesize of the request for the particular image data at least partiallybased on a resolution of the user device that requested the particularimage data.

Referring again to FIG. 12E, operation 1254 may include operation 1262depicting determining the size of the request for the particular imagedata at least partially based on a device access level of a user devicethat requested at least a portion of the particular image data. Forexample, FIG. 7, e.g., FIG. 7E, shows size of request for particularimage determining at least partially based on user device access levelmodule 762 determining the size of the request for the particular imagedata at least partially based on a device access level of a user devicethat requested at least a portion of the particular image data (e.g.,whether the user has paid for the service, or what level of service theuser has subscribed to, or whether other “superusers” are present thatdemand higher bandwidth and receive priority in receiving images).

Referring again to FIG. 12E, operation 1254 may include operation 1264depicting determining the size of the request for the particular imagedata at least partially based on an available amount of bandwidth forcommunication with the image sensor array. For example, FIG. 7, e.g.,FIG. 7E, shows size of request for particular image determining at leastpartially based on available bandwidth module 764 determining the sizeof the request for the particular image data at least partially based onan available amount of bandwidth for communication with the image sensorarray (e.g., a set of twenty-five image sensors lined on each face of atwenty-five sided polygonal structure)

Referring again to FIG. 12E, operation 1254 may include operation 1266depicting determining the size of the request for the particular imagedata at least partially based on an amount of time that a user devicethat requested at least a portion of the particular image data hasrequested image data. For example, FIG. 7, e.g., FIG. 7E, shows size ofrequest for particular image determining at least partially based ondevice usage time module 766 determining the size of the request for theparticular image data at least partially based on an amount of time thata user device that requested at least a portion of the particular imagedata has requested image data (e.g., devices that have waited longer mayget preference; or, once a device has been sent a requested image, thatdevice may move to the back of a queue for image data requests).

Referring again to FIG. 12E, operation 1254 may include operation 1268depicting determining the size of the request for the particular imagedata at least partially based on an available amount of bandwidth forcommunication with a user device that requested at least a portion ofthe particular image data. For example, FIG. 7, e.g., FIG. 7E, showssize of request for particular image determining at least partiallybased on device available bandwidth module 768 determining the size ofthe request for the particular image data at least partially based on anavailable amount of bandwidth for communication with a user device thatrequested at least a portion of the particular image data (e.g., basedon a connection between the user device and the server, e.g., if thebandwidth to the user device is a limiting factor, that may be takeninto account and used in setting the size of the request for theparticular image data).

FIGS. 13A-13C depict various implementations of operation 1006,depicting receiving only the particular image data from the image sensorarray, according to embodiments. Referring now to FIG. 13A, operation1006 may include operation 1302 depicting receiving only the particularimage data from the image sensor array, wherein data from the sceneother than the particular image data is discarded. For example, FIG. 8,e.g., FIG. 8A, shows particular image data from the image sensor arrayin which other image data is discarded receiving module 802 receivingonly the particular image data from the image sensor array, wherein datafrom the scene other than the particular image data is discarded (e.g.,the data may be stored, at least temporarily, but is not stored in aplace where overwriting will be prevented, as in a persistent memory).

Referring again to FIG. 13A, operation 1006 may include operation 1304depicting receiving only the particular image data from the image sensorarray, wherein data from the scene other than the particular image datais stored at the image sensor array. For example, FIG. 8, e.g., FIG. 8A,shows particular image data from the image sensor array in which otherimage data is stored at the image sensor array receiving module 804receiving only the particular image data (e.g., an image of a polar bearand a penguin) from the image sensor array (e.g., twenty five CMOSsensors), wherein data from the scene (e.g., an Antarctic ice floe)other than the particular image data is stored at the image sensor array(e.g., a grouping of twenty-five CMOS sensors).

Referring again to FIG. 13A, operation 1006 may include operation 1306depicting receiving the particular image data from the image sensorarray in near-real time. For example, FIG. 8, e.g., FIG. 8A, showsparticular image data from the image sensor array exclusivenear-real-time receiving module 806 receiving the particular image datafrom the image sensor array in near-real time (e.g., not necessarily assomething is happening, but near enough to give an appearance ofreal-time).

Referring now to FIG. 13B, operation 1006 may include operation 1308depicting receiving the particular image data from the image sensorarray in near-real time. For example, FIG. 8, e.g., FIG. 8B, showsparticular image data from the image sensor array exclusivenear-real-time receiving module 808 receiving the particular image datafrom the image sensor array in near real time receiving the particularimage data (e.g., an image of a person walking across a street capturedin a live street view setting) from the image sensor array (e.g., twohundred ten-megapixel sensors) in near-real time.

Referring again to FIG. 13B, operation 1006 may include operation 1310,which may appear in conjunction with operation 1308, operation 1310depicting retrieving data from the scene other than the particular imagedata at a later time. For example, FIG. 8, e.g., FIG. 8B, shows datafrom the scene other than the particular image data retrieving at alater time module 810 retrieving data from the scene (e.g., a scene of amountain pass) other than the particular image data (e.g., the data thatwas not requested—e.g., data that no user requested but that wascaptured by the image sensor array, but not transmitted to the remoteserver) at a later time (e.g., at an off-peak time when more bandwidthis available, e.g., fewer users are using the system).

Referring again to FIG. 13B, operation 1310 may include operation 1312depicting retrieving data from the scene other than the particular imagedata at a time at which bandwidth is available to the image sensorarray. For example, FIG. 8, e.g., FIG. 8B, shows data from the sceneother than the particular image data retrieving at a time of availablebandwidth module 812 retrieving data from the scene other than theparticular image data (e.g., data that was not requested) at a time atwhich bandwidth is available to the image sensor array (e.g., the imagesensor array is not using all of its allotted bandwidth to handlerequests for portions of the scene, and has available bandwidth totransmit data that can be retrieved that is other than the requestedparticular image data).

Referring again to FIG. 13B, operation 1310 may include operation 1314depicting retrieving data from the scene other than the particular imagedata at a time at that represents off-peak usage for the image sensorarray. For example, FIG. 8, e.g., FIG. 8B, shows data from the sceneother than the particular image data retrieving at an off-peak usagetime of the image sensor array module 814 retrieving data from the sceneother than the particular image data (e.g., data that was not requested)at a time that represents off-peak usage (e.g., the image sensor arraymay be capturing a city street, so off-peak usage would be at night; orthe image sensor array may be a security camera, so off-peak usage maybe the middle of the day, or off-peak usage may be flexible based onprevious time period analysis, e.g., could also mean any time the imagesensor array is not using all of its allotted bandwidth to handlerequests for portions of the scene, and has available bandwidth totransmit data that can be retrieved that is other than the requestedparticular image data) for the image sensor array.

Referring again to FIG. 13B, operation 1310 may include operation 1316depicting retrieving data from the scene other than the particular imagedata at a time when no particular image data is requested. For example,FIG. 8, e.g., FIG. 8B, shows data from the scene other than theparticular image data retrieving at a time when no particular image datarequests are present at the image sensor array module 816 retrievingdata from the scene other than the particular image data at a time whenno particular image data is requested.

Referring again to FIG. 13B, operation 1310 may include operation 1318depicting retrieving data from the scene other than the particular imagedata at time at which fewer users are requesting particular image datathan for which the image sensor array has capacity. For example, FIG. 8,e.g., FIG. 8B, shows data from the scene other than the particular imagedata retrieving at a time of available image sensor array capacitymodule 818 retrieving data from the scene other than the particularimage data at time at which fewer users are requesting particular imagedata than for which the image sensor array has capacity.

Referring now to FIG. 13C, operation 1006 may include operation 1320depicting receiving only the particular image data that includes audiodata from the sensor array. For example, FIG. 8, e.g., FIG. 8C, showsparticular image data that includes audio data from the image sensorarray exclusive receiving module 820 receiving only the particular imagedata (e.g., image data from a watering hole) that includes audio data(e.g., sound data, e.g., as picked up by a microphone) from the sensorarray (e.g., the image sensor array may include one or more microphonesor other sound-collecting devices, either separately from or linked toimage capturing sensors).

Referring again to FIG. 13C, operation 1006 may include operation 1322depicting receiving only the particular image data that was determinedto contain a particular requested image object from the image sensorarray. For example, FIG. 8, e.g., FIG. 8C, shows particular image datathat was determined to contain a particular requested image object fromthe image sensor array exclusive receiving module 822 receiving only theparticular image data that was determined to contain a particularrequested image object (e.g., a particular football player from afootball game that is the scene) from the image sensor array.

Referring again to FIG. 13C, operation 1322 may include operation 1324depicting receiving only the particular image data that was determinedto contain a particular requested image object by the image sensorarray. For example, FIG. 8, e.g., FIG. 8C, shows particular image datathat was determined to contain a particular requested image object bythe image sensor array exclusive receiving module 824. receiving onlythe particular image data that was determined to contain a particularrequested image object (e.g., a lion at a watering hole) by the imagesensor array (e.g., the image sensor array performs the patternrecognition and identifies the particular image data, which may onlyhave been identified as “the image data that contains the lion,” andonly that particular image data is transmitted and thus received by theserver).

FIGS. 14A-14E depict various implementations of operation 1008,depicting transmitting the received particular image data to at leastone requestor, according to embodiments. Referring now to FIG. 14A,operation 1008 may include operation 1402 depicting transmitting thereceived particular image data to a user device. For example, FIG. 9,e.g., FIG. 9A, shows received particular image data transmitting to atleast one user device requestor module 902 transmitting the receivedparticular image data (e.g., an image of a quarterback at a NationalFootball League game) to a user device (e.g., a television connected tothe internet).

Referring again to FIG. 14A, operation 1402 may include operation 1404depicting transmitting at least a portion of the received particularimage data to a user device that requested the particular image data.For example, FIG. 9, e.g., FIG. 9A, shows received particular image datatransmitting to at least one user device that requested at least aportion of the received particular data requestor module 904transmitting at least a portion of the received particular image data(e.g., a portion that corresponds to a particular request received froma device, e.g., a request for a particular segment of the scene thatshows a lion at a watering hole) to a user device (e.g., a computerdevice with a CPU and monitor) that requested the particular image data(e.g., the computer device requested the portion of the scene at whichthe lion is visible).

Referring again to FIG. 14A, operation 1008 may include operation 1406depicting separating the received particular image data into a set ofone or more requested images. For example, FIG. 9, e.g., FIG. 9A, showsseparation of the received particular data into set of one or morerequested images executing module 906 separating the received particularimage data into a set of one or more requested images (e.g., if therewere five requests for portions of the scene data, and some of therequests overlapped, the image data may be duplicated and packaged suchthat each requesting device receives the pixels that were requested).

Referring again to FIG. 14A, operation 1008 may include operation 1408,which may appear in conjunction with operation 1406, operation 1408depicting transmitting at least one image of the set of one or morerequested images to a particular requestor that requested the at leastone image. For example, FIG. 9, e.g., FIG. 9A, shows at least one imageof the set of one or more requested images transmitting to a particularrequestor that requested the one or more images transmitting module 908transmitting at least one image of the set of one or more requestedimages to a particular requestor (e.g., a person operating a “virtualcamera” that lets the person “see” the scene through the lens of acamera, even though the camera is temporally separated from the imagesensor array, possibly by a large distance, because the image istransmitted to the camera).

Referring again to FIG. 14A, operation 1406 may include operation 1410depicting separating the received particular image data into a firstrequested image and a second requested image. For example, FIG. 9, e.g.,FIG. 9A, shows separation of the received particular data into a firstrequested image and a second requested image executing module 910separating the received particular image data (e.g., image data from ajungle oasis) into a first requested image (e.g., an image of a lion)and a second requested image (e.g., an image of a hippopotamus).

Referring again to FIG. 14A, operation 1008 may include operation 1412depicting transmitting the received particular image data to a userdevice that requested an image that is part of the received particularimage data. For example, FIG. 9, e.g., FIG. 9A, shows receivedparticular image data transmitting to at least one user device thatrequested image data that is part of the received particular image datamodule 912 transmitting the received particular image data to a userdevice that requested an image that is part of the received particularimage data.

Referring now to FIG. 14B, operation 1008 may include operation 1414depicting transmitting a first portion of the received particular imagedata to a first requestor. For example, FIG. 9, e.g., FIG. 9B, showsfirst portion of received particular image data transmitting to a firstrequestor module 914 transmitting a first portion (e.g., a part of ananimal oasis that contains a zebra) of the received particular imagedata (e.g., image data from the oasis that contains a zebra) to a firstrequestor (e.g., device that requested video feed that is the portion ofthe oasis that contains the zebra, e.g., a television device).

Referring again to FIG. 14B, operation 1008 may include operation 1416,which may appear in conjunction with operation 1414, operation 1416depicting transmitting a second portion of the received particular imagedata to a second requestor. For example, FIG. 9, e.g., FIG. 9B, showssecond portion of received particular image data transmitting to asecond requestor module 916 transmitting a second portion (e.g., aportion of the oasis that contains birds) of the received particularimage data (e.g., image data from the oasis) to a second requestor(e.g., a device that requested the image that is the portion of theoasis that contains birds, e.g., a tablet device).

Referring again to FIG. 14B, operation 1414 may include operation 1418depicting transmitting the first portion of the received particularimage data to the first requestor that requested the first portion ofthe received particular image data. For example, FIG. 9, e.g., FIG. 9B,shows first portion of received particular image data transmitting to afirst requestor that requested the first portion module 918 transmittingthe first portion of the received particular image data (e.g., a portionthat contains a particular landmark in a virtual tourism setting) to thefirst requestor that requested the first portion of the receivedparticular image data.

Referring again to FIG. 14B, operation 1418 may include operation 1420depicting transmitting an image that contains a particular footballplayer to a television device that is configured to display a footballgame and that requested the image that contains the particular footballplayer. For example, FIG. 9, e.g., FIG. 9B, shows portion of receivedparticular image data that includes a particular football playertransmitting to a television device that requested the football playerfrom a football game module 920 transmitting an image that contains aparticular football player to a television device that is configured todisplay a football game and that requested the image that contains theparticular football player.

Referring again to FIG. 14B, operation 1416 may include operation 1422depicting transmitting the second portion of the received particularimage data to the second requestor that requested the second portion ofthe received particular image data. For example, FIG. 9, e.g., FIG. 9B,shows second portion of received particular image data transmitting tothe second requestor that requested the second portion module 922transmitting the second portion of the received particular image data(e.g., the portion of the received particular image data that includesthe lion) to the second requestor that requested the second portion ofthe received particular image data (e.g., a person watching the feed ontheir television).

Referring again to FIG. 14B, operation 1422 may include operation 1424depicting transmitting an image that contains a view of a motor vehicleto a tablet device that requested a street view image of a particularcorner of a city. For example, FIG. 9, e.g., FIG. 9B, shows portion thatcontains a view of a motor vehicle transmitting to the second requestorthat is a tablet device that requested the view of the motor vehiclemodule 924 transmitting an image that contains a view of a motor vehicle(e.g., a Honda Accord) to a tablet device that requested a street viewimage of a particular corner of a city (e.g., Alexandria, Va.).

Referring again to FIG. 14B, operation 1008 may include operation 1426depicting transmitting at least a portion of the received particularimage data without alteration to at least one requestor. For example,FIG. 9, e.g., FIG. 9B, shows received particular image data unalteredtransmitting to at least one requestor module 926 transmitting at leasta portion of the received particular image data (e.g., an image ofanimals at an oasis) without alteration (e.g., without altering how theimage appears to human eyes, e.g., there may be data manipulation thatis not visible) to at least one requestor (e.g., the device thatrequested the image, e.g., a mobile device).

Referring now to FIG. 14C, operation 1008 may include operation 1428depicting adding supplemental data to at least a portion of the receivedparticular image data to generate transmission image data. For example,FIG. 9, e.g., FIG. 9C, shows supplemental data addition to at least aportion of the received particular image data to generate transmissionimage data facilitating module 928 adding supplemental data (e.g.,context data, or advertisement data, or processing assistance data, ordata regarding how to display or cache the image, whether visible in theimage or embedded therein, or otherwise associated with the image) to atleast a portion of the received particular image data (e.g., images froman animal watering hole) to generate transmission image data (e.g.,image data that will be transmitted to the requestor, e.g., a user of adesktop computer).

Referring again to FIG. 14C, operation 1008 may include operation 1430,which may appear in conjunction with operation 1428, operation 1430depicting transmitting the generated transmission image data to at leastone requestor. For example, FIG. 9, e.g., FIG. 9C, shows generatedtransmission image data transmitting to at least one requestor module930 transmitting the generated transmission image data to at least onerequestor transmitting the generated transmission image data (e.g.,image data of a football player at a football game with statistical dataof that football player overlaid in the image) to at least one requestor(e.g., a person watching the game on their mobile tablet device).

Referring again to FIG. 14C, operation 1428 may include operation 1432depicting adding advertisement data to at least a portion of thereceived particular image data to generate transmission image data. Forexample, FIG. 9, e.g., FIG. 9C, shows advertisement data addition to atleast a portion of the received particular image data to generatetransmission image data facilitating module 932 adding advertisementdata (e.g., data for an advertisement for buying tickets to the nextsoccer game and an advertisement for buying a soccer jersey of theplayer that is pictured) to at least a portion of the receivedparticular image data (e.g., images of a soccer game and/or players inthe soccer game) to generate transmission image data.

Referring again to FIG. 14C, operation 1432 may include operation 1434depicting adding context-based advertisement data that is at leastpartially based on the received particular image data to at least theportion of the received particular image data. For example, FIG. 9,e.g., FIG. 9C, shows context-based advertisement data addition to atleast a portion of the received particular image data to generatetransmission image data facilitating module 934 adding context-basedadvertisement data (e.g., an ad for travel services to a place that isbeing viewed in a virtual tourism setting, e.g., the Great Pyramids)that is at least partially based on the received particular image data(e.g., visual image data from the Great Pyramids) to at least theportion of the received particular image data.

Referring again to FIG. 14C, operation 1434 may include operation 1436depicting adding an animal rights donation fund advertisement data thatis at least partially based on the received particular image data of atiger at a jungle oasis, to the received particular image data of thetiger at the jungle oasis. For example, FIG. 9, e.g., FIG. 9C, showsanimal rights donation fund advertisement data addition to at least aportion of the received particular image data that includes a jungletiger at an oasis to generate transmission image data facilitatingmodule 936 adding an animal rights donation fund advertisement data thatis at least partially based on the received particular image data of atiger at a jungle oasis, to the received particular image data of thetiger at the jungle oasis.

Referring again to FIG. 14C, operation 1428 may include operation 1438depicting adding related visual data related to the received particularimage data to at least a portion of the received particular image datato generate transmission image data. For example, FIG. 9, e.g., FIG. 9C,shows related visual data addition to at least a portion of the receivedparticular image data to generate transmission image data facilitatingmodule 938 adding related visual data (e.g., the name of an animal beingshown, or a make and model year of a car being shown, or, if a productis shown in the frame, the name of the website that has it for thecheapest price right now) related to the received particular image data(e.g., an animal, a car, or a product) to at least a portion of thereceived particular image data to generate transmission image data(e.g., data to be transmitted to the receiving device).

Referring again to FIG. 14C, operation 1438 may include operation 1440depicting adding fantasy football statistical data to the receivedparticular image data of a football quarterback that appears in thereceived particular image data of the quarterback in a football game togenerate the transmission image data. For example, FIG. 9, e.g., FIG.9C, shows related fantasy football statistical data addition to at leasta portion of the received particular image data of a quarterback data togenerate transmission image data facilitating module 940 adding fantasyfootball statistical data (e.g., passes completed, receptions, rushingyards gained, receiving yards gained, total points scored, player name,etc.) to the received particular image data of a football quarterbackthat appears in the received particular image data of the quarterback ina football game to generate the transmission image data (e.g., imagedata that is to be transmitted to the requesting device, e.g., atelevision).

Referring now to FIG. 14D, operation 1008 may include operation 1442depicting modifying data of a portion of the received particular imagedata to generate transmission image data. For example, FIG. 9, e.g.,FIG. 9D, shows portion of received particular image data modification togenerate transmission image data facilitating module 942 modifying data(e.g., adding to, subtracting from, or changing the data of acharacteristic of, e.g., alpha data, color data, saturation data, eitheron individual bytes or on the image as a whole) of a portion of thereceived particular image data (e.g., the image data sent from thecamera array) to generate transmission image data (e.g., data to betransmitted to the device that requested the data, e.g., a smartphonedevice).

Referring again to FIG. 14D, operation 1008 may include operation 1444depicting transmitting at the generated transmission image data to atleast one requestor. For example, FIG. 9, e.g., FIG. 9D, shows generatedtransmission image data transmitting to at least one requestor module944 transmitting the generated transmission image data (e.g., the imagedata that was generated by the server device to transmit to therequesting device) to at least one requestor (e.g., the requestingdevice, e.g., a laptop computer of a family at home running a virtualtourism program in a web page).

Referring again to FIG. 14D, operation 1442 may include operation 1446depicting performing image manipulation modifications of the receivedparticular image data to generate transmission image data. For example,FIG. 9, e.g., FIG. 9D, shows portion of received particular image dataimage manipulation modification to generate transmission image datafacilitating module 946 performing image manipulation modifications(e.g., editing a feature of a captured image) of the received particularimage data (e.g., a live street view of an area with a lot of shadingfrom tall skyscrapers) to generate transmission image data (e.g., theimage data to be transmitted to the device that requested the data,e.g., a camera device).

Referring again to FIG. 14D, operation 1446 may include operation 1448depicting performing contrast balancing on the received particular imagedata to generate transmission image data. For example, FIG. 9, e.g.,FIG. 9D, shows portion of received particular image data contrastbalancing modification to generate transmission image data facilitatingmodule 948 performing contrast balancing on the received particularimage data (e.g., a live street view of an area with a lot of shadingfrom tall skyscrapers) to generate transmission image data (e.g., theimage data to be transmitted to the device that requested the data,e.g., a camera device).

Referring again to FIG. 14D, operation 1446 may include operation 1450depicting performing color modification balancing on the receivedparticular image data to generate transmission image data. For example,FIG. 9, e.g., FIG. 9D, shows portion of received particular image datacolor modification balancing to generate transmission image datafacilitating module 950 performing color modification balancing on thereceived particular image data (e.g., an image of a lion at an animalwatering hole) to generate transmission image data (e.g., the image datathat will be transmitted to the device).

Referring again to FIG. 14D, operation 1442 may include operation 1452depicting redacting at least a portion of the received particular imagedata to generate the transmission image data. For example, FIG. 9, e.g.,FIG. 9D, shows portion of received particular image data redaction togenerate transmission image data facilitating module 952 redacting(e.g., deleting, smoothing over, blurring, performing any sort of imagemanipulation operation upon, or any other operation designed to obscureany feature of data associated with the tank, including, but not limitedto, removing or overwriting the data associated with the tank entirely)at least a portion of the received particular image data to generate thetransmission image data (e.g., the image data that will be transmittedto the device or designated for transmission to the device).

Referring again to FIG. 14D, operation 1452 may include operation 1454depicting redacting at least a portion of the received particular imagedata based on a security clearance level of the requestor. For example,FIG. 9, e.g., FIG. 9D, shows portion of received particular image dataredaction to generate transmission image data based on a securityclearance level of the requestor facilitating module 954 redacting(e.g., deleting, smoothing over, blurring, performing any sort of imagemanipulation operation upon, or any other operation designed to obscureany feature of data associated with the tank, including, but not limitedto, removing or overwriting the data associated with the tank entirely)at least a portion of the received particular image data (e.g., thefaces of people, or the license plates of cars) based on a securityclearance level of the requestor (e.g., a device that requested theimage may have a security clearance based on what that device is allowedto view, and if the security clearance level is below a certainthreshold, data like license plates and people's faces may be redacted).

Referring again to FIG. 14D, operation 1454 may include operation 1456depicting redacting a tank from the received particular image data thatincludes a satellite image that includes a military base, based on aninsufficient security clearance level of a device that requested theparticular image data. For example, FIG. 9, e.g., FIG. 9D, shows portionof received satellite image data that includes a tank redaction togenerate transmission image data based on a security clearance level ofthe requestor facilitating module 956 redacting (e.g., deleting,smoothing over, blurring, performing any sort of image manipulationoperation upon, or any other operation designed to obscure any featureof data associated with the tank, including, but not limited to,removing or overwriting the data associated with the tank entirely) atank from the received particular image data that includes a satelliteimage (e.g., the image sensor array that captured the image is at leastpartially mounted on a satellite) that includes a military base, basedon an insufficient security clearance level (e.g., some data indicatesthat the device does not have a security level sufficient to approveseeing the tank) of a device that requested the particular image data).

Referring now to FIG. 14E, operation 1008 may include operation 1458depicting transmitting a lower-resolution version of the receivedparticular image data to the at least one requestor. For example, FIG.9, e.g., FIG. 9E, shows lower-resolution version of received particularimage data transmitting to at least one requestor module 958transmitting a lower-resolution version (e.g., a version of the imagedata that is at a lower resolution than what the device that requestedthe particular image data is capable of displaying) of the receivedparticular image data (e.g., an image of a baseball player at a baseballgame) to the at least one requestor (e.g., the device that requested thedata).

Referring again to FIG. 14E, operation 1008 may include operation 1460,which may appear in conjunction with operation 1458, operation 1460depicting transmitting a full-resolution version of the receivedparticular image data to the at least one requestor. For example, FIG.9, e.g., FIG. 9F, shows full-resolution version of received particularimage data transmitting to at least one requestor module 960transmitting a full-resolution version (e.g., a version that is at aresolution of the device that requested the image) of the receivedparticular image data (e.g., an image of an animal at an animal oasis).

All of the above U.S. patents, U.S. patent application publications,U.S. patent applications, foreign patents, foreign patent applicationsand non-patent publications referred to in this specification and/orlisted in any Application Data Sheet, are incorporated herein byreference, to the extent not inconsistent herewith.

The foregoing detailed description has set forth various embodiments ofthe devices and/or processes via the use of block diagrams, flowcharts,and/or examples. Insofar as such block diagrams, flowcharts, and/orexamples contain one or more functions and/or operations, it will beunderstood by those within the art that each function and/or operationwithin such block diagrams, flowcharts, or examples can be implemented,individually and/or collectively, by a wide range of hardware, software(e.g., a high-level computer program serving as a hardwarespecification), firmware, or virtually any combination thereof, limitedto patentable subject matter under 35 U.S.C. 101. In an embodiment,several portions of the subject matter described herein may beimplemented via Application Specific Integrated Circuits (ASICs), FieldProgrammable Gate Arrays (FPGAs), digital signal processors (DSPs), orother integrated formats. However, those skilled in the art willrecognize that some aspects of the embodiments disclosed herein, inwhole or in part, can be equivalently implemented in integratedcircuits, as one or more computer programs running on one or morecomputers (e.g., as one or more programs running on one or more computersystems), as one or more programs running on one or more processors(e.g., as one or more programs running on one or more microprocessors),as firmware, or as virtually any combination thereof, limited topatentable subject matter under 35 U.S.C. 101, and that designing thecircuitry and/or writing the code for the software (e.g., a high-levelcomputer program serving as a hardware specification) and or firmwarewould be well within the skill of one of skill in the art in light ofthis disclosure. In addition, those skilled in the art will appreciatethat the mechanisms of the subject matter described herein are capableof being distributed as a program product in a variety of forms, andthat an illustrative embodiment of the subject matter described hereinapplies regardless of the particular type of signal bearing medium usedto actually carry out the distribution. Examples of a signal bearingmedium include, but are not limited to, the following: a recordable typemedium such as a floppy disk, a hard disk drive, a Compact Disc (CD), aDigital Video Disk (DVD), a digital tape, a computer memory, etc.; and atransmission type medium such as a digital and/or an analogcommunication medium (e.g., a fiber optic cable, a waveguide, a wiredcommunications link, a wireless communication link (e.g., transmitter,receiver, transmission logic, reception logic, etc.), etc.)

While particular aspects of the present subject matter described hereinhave been shown and described, it will be apparent to those skilled inthe art that, based upon the teachings herein, changes and modificationsmay be made without departing from the subject matter described hereinand its broader aspects and, therefore, the appended claims are toencompass within their scope all such changes and modifications as arewithin the true spirit and scope of the subject matter described herein.It will be understood by those within the art that, in general, termsused herein, and especially in the appended claims (e.g., bodies of theappended claims) are generally intended as “open” terms (e.g., the term“including” should be interpreted as “including but not limited to,” theterm “having” should be interpreted as “having at least,” the term“includes” should be interpreted as “includes but is not limited to,”etc.).

It will be further understood by those within the art that if a specificnumber of an introduced claim recitation is intended, such an intentwill be explicitly recited in the claim, and in the absence of suchrecitation no such intent is present. For example, as an aid tounderstanding, the following appended claims may contain usage of theintroductory phrases “at least one” and “one or more” to introduce claimrecitations. However, the use of such phrases should not be construed toimply that the introduction of a claim recitation by the indefinitearticles “a” or “an” limits any particular claim containing suchintroduced claim recitation to claims containing only one suchrecitation, even when the same claim includes the introductory phrases“one or more” or “at least one” and indefinite articles such as “a” or“an” (e.g., “a” and/or “an” should typically be interpreted to mean “atleast one” or “one or more”); the same holds true for the use ofdefinite articles used to introduce claim recitations. In addition, evenif a specific number of an introduced claim recitation is explicitlyrecited, those skilled in the art will recognize that such recitationshould typically be interpreted to mean at least the recited number(e.g., the bare recitation of “two recitations,” without othermodifiers, typically means at least two recitations, or two or morerecitations).

Furthermore, in those instances where a convention analogous to “atleast one of A, B, and C, etc.” is used, in general such a constructionis intended in the sense one having skill in the art would understandthe convention (e.g., “a system having at least one of A, B, and C”would include but not be limited to systems that have A alone, B alone,C alone, A and B together, A and C together, B and C together, and/or A,B, and C together, etc.). In those instances where a conventionanalogous to “at least one of A, B, or C, etc.” is used, in general sucha construction is intended in the sense one having skill in the artwould understand the convention (e.g., “a system having at least one ofA, B, or C” would include but not be limited to systems that have Aalone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.). It will be furtherunderstood by those within the art that typically a disjunctive wordand/or phrase presenting two or more alternative terms, whether in thedescription, claims, or drawings, should be understood to contemplatethe possibilities of including one of the terms, either of the terms, orboth terms unless context dictates otherwise. For example, the phrase “Aor B” will be typically understood to include the possibilities of “A”or “B” or “A and B.”

With respect to the appended claims, those skilled in the art willappreciate that recited operations therein may generally be performed inany order. Also, although various operational flows are presented in asequence(s), it should be understood that the various operations may beperformed in other orders than those which are illustrated, or may beperformed concurrently. Examples of such alternate orderings may includeoverlapping, interleaved, interrupted, reordered, incremental,preparatory, supplemental, simultaneous, reverse, or other variantorderings, unless context dictates otherwise. Furthermore, terms like“responsive to,” “related to,” or other past-tense adjectives aregenerally not intended to exclude such variants, unless context dictatesotherwise.

This application may make reference to one or more trademarks, e.g., aword, letter, symbol, or device adopted by one manufacturer or merchantand used to identify and/or distinguish his or her product from those ofothers. Trademark names used herein are set forth in such language thatmakes clear their identity, that distinguishes them from commondescriptive nouns, that have fixed and definite meanings, or, in many ifnot all cases, are accompanied by other specific identification usingterms not covered by trademark. In addition, trademark names used hereinhave meanings that are well-known and defined in the literature, or donot refer to products or compounds for which knowledge of one or moretrade secrets is required in order to divine their meaning. Alltrademarks referenced in this application are the property of theirrespective owners, and the appearance of one or more trademarks in thisapplication does not diminish or otherwise adversely affect the validityof the one or more trademarks. All trademarks, registered orunregistered, that appear in this application are assumed to include aproper trademark symbol, e.g., the circle R or bracketed capitalization(e.g., [trademark name]), even when such trademark symbol does notexplicitly appear next to the trademark. To the extent a trademark isused in a descriptive manner to refer to a product or process, thattrademark should be interpreted to represent the corresponding productor process as of the date of the filing of this patent application.

Throughout this application, the terms “in an embodiment,” ‘in oneembodiment,” “in an embodiment,” “in several embodiments,” “in at leastone embodiment,” “in various embodiments,” and the like, may be used.Each of these terms, and all such similar terms should be construed as“in at least one embodiment, and possibly but not necessarily allembodiments,” unless explicitly stated otherwise. Specifically, unlessexplicitly stated otherwise, the intent of phrases like these is toprovide non-exclusive and non-limiting examples of implementations ofthe invention. The mere statement that one, some, or may embodimentsinclude one or more things or have one or more features, does not implythat all embodiments include one or more things or have one or morefeatures, but also does not imply that such embodiments must exist. Itis a mere indicator of an example and should not be interpretedotherwise, unless explicitly stated as such.

Those skilled in the art will appreciate that the foregoing specificexemplary processes and/or devices and/or technologies arerepresentative of more general processes and/or devices and/ortechnologies taught elsewhere herein, such as in the claims filedherewith and/or elsewhere in the present application.

1-326. (canceled)
 327. A device, comprising: a request for particularimage data that is part of a scene acquiring module; a request forparticular image data transmitting to an image sensor array moduleconfigured to transmit the request to the image sensor array thatincludes more than one image sensor and that is configured to capturethe scene that is larger than the requested particular image data; aparticular image data from the image sensor array exclusive receivingmodule; and a received particular image data transmitting to at leastone requestor module.
 328. (canceled)
 329. (canceled)
 330. (canceled)331. (canceled)
 332. (canceled)
 333. (canceled)
 334. (canceled) 335.(canceled)
 336. (canceled)
 337. The device of claim 327, wherein saidrequest for particular image data that is part of a scene acquiringmodule comprises: a request for particular image data that is part of aparticular scene acquiring module, wherein the request particular sceneis a representation of the image data collected by the array of morethan one image sensor acquiring module.
 338. The device of claim 337,wherein said request for particular image data that is part of aparticular scene acquiring module comprises: a request for particularimage data that is part of a particular scene acquiring module, whereinthe request particular scene is a sampling of the image data collectedby the array of more than one image sensor.
 339. (canceled) 340.(canceled)
 341. (canceled)
 342. The device of claim 327, wherein saidrequest for particular image data that is part of a scene acquiringmodule comprises: a request for particular image data that is part of ascene that is an area street view acquiring module.
 343. (canceled) 344.(canceled)
 345. The device of claim 327, wherein said request forparticular image data that is part of a scene acquiring modulecomprises: a request for particular image data acquiring module, whereinthe particular image data is an image that is a portion of the scene.346. (canceled)
 347. The device of claim 345, wherein said request forparticular image data acquiring module, wherein the particular imagedata is an image that is a portion of the scene comprises: a request forparticular image data of the scene acquiring module, wherein theparticular image data includes image data of a license plate of avehicle, and the scene is a highway bridge.
 348. The device of claim327, wherein said request for particular image data that is part of ascene acquiring module comprises: a request for particular image objectlocated in the scene acquiring module; and a particular image data ofthe scene that contains the particular image object determining module.349. (canceled)
 350. The device of claim 348, wherein said request forparticular image object located in the scene acquiring module comprises:a request for a basketball object located in the scene acquiring module,wherein the scene is a basketball arena.
 351. (canceled)
 352. (canceled)353. (canceled)
 354. (canceled)
 355. The device of claim 348, whereinsaid particular image data of the scene that contains the particularimage object determining module comprises: a particular image data ofthe scene that contains the particular image object determining moduleconfigured to determine the particular image data of the scene thatcontains the particular image object through identification of theparticular image object in cached scene data.
 356. The device of claim355, wherein said particular image data of the scene that contains theparticular image object determining module configured to determine theparticular image data of the scene that contains the particular imageobject through identification of the particular image object in cachedscene data comprises: a particular image data of the scene that containsthe particular image object determining module configured to determinethe particular image data of the scene that contains the particularimage object through identification of the particular image object incached scene data that was previously transmitted from the image sensorarray that includes more than one image sensor.
 357. (canceled)
 358. Thedevice of claim 327, wherein said request for particular image data thatis part of a scene acquiring module comprises: a first request for firstparticular image data from a first requestor receiving module; and asecond request for first particular image data from a different secondrequestor receiving module, wherein the second requestor is differentthan the first requestor.
 359. The device of claim 327, wherein saidrequest for particular image data that is part of a scene acquiringmodule comprises: a first received request and second received requestcombining module configured to combine a received first request forfirst particular image data from the scene and a received second requestfor second particular image data from the scene.
 360. The device ofclaim 359, wherein said first received request and second receivedrequest combining module configured to combine a received first requestfor first particular image data from the scene and a received secondrequest for second particular image data from the scene comprises: afirst received request and second received request combining module thereceived first request configured to combine the first received requestfor first particular image data from the scene and the received secondrequest for second particular image data from the scene into the requestfor particular image data that consolidates overlapping requested imagedata.
 361. The device of claim 327, wherein said request for particularimage data that is part of a scene acquiring module comprises: a firstrequest for first particular image data and second request for secondparticular image data receiving module; and a received first request andreceived second request combining module configured to combine thereceived first request and the received second request into the requestfor particular image data.
 362. The device of claim 361, wherein saidreceived first request and received second request combining moduleconfigured to combine the received first request and the received secondrequest into the request for particular image data comprises: a receivedfirst request and received second request common pixel deduplicatingmodule configured to remove common pixel data between the received firstrequest and the received second request.
 363. (canceled)
 364. (canceled)365. (canceled)
 366. (canceled)
 367. The device of claim 327, whereinsaid request for particular image data transmitting to an image sensorarray module configured to transmit the request to the image sensorarray that includes more than one image sensor and that is configured tocapture the scene that is larger than the requested particular imagedata comprises: a request for particular image data transmitting to animage sensor array module configured to transmit the request for theparticular image data of the scene to the image sensor array thatincludes more than one image sensor and that is configured to capture animage that is larger than the requested image data.
 368. (canceled) 369.(canceled)
 370. (canceled)
 371. (canceled)
 372. (canceled) 373.(canceled)
 374. (canceled)
 375. The device of claim 327, wherein saidrequest for particular image data transmitting to an image sensor arraymodule configured to transmit the request to the image sensor array thatincludes more than one image sensor and that is configured to capturethe scene that is larger than the requested particular image datacomprises: a request for particular image data transmitting to an imagesensor array module configured to transmit the request for theparticular image data of the scene to the image sensor array thatincludes more than one image sensor and that is configured to capturethe scene that represents more image data than the requested particularimage data.
 376. (canceled)
 377. The device of claim 375, wherein saidrequest for particular image data transmitting to an image sensor arraymodule configured to transmit the request for the particular image dataof the scene to the image sensor array that includes more than one imagesensor and that is configured to capture the scene that represents moreimage data than the requested particular image data comprises: a requestfor particular image data transmitting to an image sensor array moduleconfigured to transmit the request for the particular image data of thescene to the image sensor array that includes more than one image sensorand that is configured to capture the scene that represents more thanone hundred times as much image data as the requested particular imagedata.
 378. (canceled)
 379. The device of claim 327, wherein said requestfor particular image data transmitting to an image sensor array moduleconfigured to transmit the request to the image sensor array thatincludes more than one image sensor and that is configured to capturethe scene that is larger than the requested particular image datacomprises: a request for particular image data modifying module; and amodified request for particular image data transmitting to an imagesensor array module configured to transmit the modified request for theparticular image data to the image sensor array that includes more thanone image sensor and that is configured to capture the scene that islarger than the requested particular image data.
 380. The device ofclaim 379, wherein said request for particular image data modifyingmodule comprises: a designated image data removing from request forparticular image data module configured to remove designated image datafrom the request for the particular image data.
 381. The device of claim380, wherein said designated image data removing from request forparticular image data module configured to remove designated image datafrom the request for the particular image data comprises: a designatedimage data removing from request for particular image data moduleconfigured to remove designated image data from the request for theparticular image data based on previously stored image data. 382.(canceled)
 383. The device of claim 381, wherein said designated imagedata removing from request for particular image data module configuredto remove designated image data from the request for the particularimage data based on previously stored image data comprises: a designatedimage data removing from request for particular image data moduleconfigured to remove designated image data from the request for theparticular image data based on previously stored image data that is anearlier-in-time version of the designated image data.
 384. The device ofclaim 383, wherein said designated image data removing from request forparticular image data module configured to remove designated image datafrom the request for the particular image data based on previouslystored image data that is an earlier-in-time version of the designatedimage data comprises: a designated image data removing from request forparticular image data module configured to remove image data of one ormore static objects from the request for the particular image data thatis a view of a street, based on previously stored image data of the oneor more static objects from an earlier-in-time version captured by theimage sensor array.
 385. (canceled)
 386. (canceled)
 387. (canceled) 388.The device of claim 379, wherein said request for particular image datamodifying module comprises: a portion of the request for particularimage data that was previously stored in memory identifying moduleconfigured to identify at least one portion of the request for theparticular image data that was previously stored in a memory; and anidentified portion of the request for the particular image data removingmodule configured to removing the identified portion of the request forthe particular image data.
 389. (canceled)
 390. (canceled) 391.(canceled)
 392. The device of claim 327, wherein said request forparticular image data transmitting to an image sensor array moduleconfigured to transmit the request to the image sensor array thatincludes more than one image sensor and that is configured to capturethe scene that is larger than the requested particular image datacomprises: a size of request for particular image data determiningmodule; and a determined-size request for particular image datatransmitting to the image sensor array module configured to transmit therequest for the particular image data for which the size has beendetermined to the image sensor array that is configured to capture thescene.
 393. The device of claim 392, wherein said size of request forparticular image data determining module comprises: a size of requestfor particular image data determining module configured to determine thesize of the request for the particular image data at least partiallybased on a property of a user device that requested at least a portionof the particular image data.
 394. (canceled)
 395. (canceled) 396.(canceled)
 397. (canceled)
 398. (canceled)
 399. The device of claim 327,wherein said particular image data from the image sensor array exclusivereceiving module comprises: a particular image data from the imagesensor array exclusive receiving module configured to receive only theparticular image data from the image sensor array, wherein data from thescene other than the particular image data is discarded.
 400. The deviceof claim 327, wherein said particular image data from the image sensorarray exclusive receiving module comprises: a particular image data fromthe image sensor array exclusive receiving module configured to receiveonly the particular image data from the image sensor array, wherein datafrom the scene other than the particular image data is stored at theimage sensor array.
 401. (canceled)
 402. The device of claim 327,wherein said particular image data from the image sensor array exclusivereceiving module comprises: a particular image data from the imagesensor array exclusive near-real-time receiving module configured toreceive the particular image data from the image sensor array innear-real time; and a data from the scene other than the particularimage data retrieving at a later time module configured to retrieve datafrom the scene other than the particular image data at a later time.403. The device of claim 402, wherein said data from the scene otherthan the particular image data retrieving at a later time moduleconfigured to retrieve data from the scene other than the particularimage data at a later time comprises: a data from the scene other thanthe particular image data retrieving at a later time module configuredto retrieve data from the scene other than the particular image data ata time at which bandwidth is available to the image sensor array. 404.(canceled)
 405. (canceled)
 406. (canceled)
 407. (canceled)
 408. Thedevice of claim 327, wherein said particular image data from the imagesensor array exclusive receiving module comprises: a particular imagedata that was determined to contain a particular requested image objectfrom the image sensor array exclusive receiving module configured toreceive only the particular image data that was determined to contain aparticular requested image object from the image sensor array. 409.(canceled)
 410. (canceled)
 411. (canceled)
 412. The device of claim 327,wherein said received particular image data transmitting to at least onerequestor module comprises: a separation of the received particular datainto set of one or more requested images executing module configured toseparate the received particular image data into a set of one or morerequested images; and an at least one image of the set of one or morerequested images transmitting to a particular requestor moduleconfigured to transmit at least one image of the set of one or morerequested images to a particular requestor that requested the at leastone image.
 413. The device of claim 412, wherein said separation of thereceived particular data into set of one or more requested imagesexecuting module configured to separate the received particular imagedata into a set of one or more requested images comprises: a separationof the received particular data into a first requested image and asecond requested image executing module configured to separate thereceived particular image data into a first requested image and a secondrequested image.
 414. (canceled)
 415. The device of claim 327, whereinsaid received particular image data transmitting to at least onerequestor module comprises: a first portion of received particular imagedata transmitting to a first requestor module; and a second portion ofreceived particular image data transmitting to a second requestormodule.
 416. The device of claim 415, wherein said first portion ofreceived particular image data transmitting to a first requestor modulecomprises: a first portion of received particular image datatransmitting to a first requestor that requested the first portionmodule configured to transmit the first portion of the receivedparticular image data to the first requestor that requested the firstportion of the received particular image data.
 417. (canceled) 418.(canceled)
 419. (canceled)
 420. (canceled)
 421. The device of claim 327,wherein said received particular image data transmitting to at least onerequestor module comprises: a supplemental data addition to at least aportion of the received particular image data facilitating moduleconfigured to add supplemental data to at least a portion of thereceived particular image data to generate transmission image data; anda generated transmission image data transmitting to at least onerequestor module configured to transmit the generated transmission imagedata to at least one requestor.
 422. The device of claim 421, whereinsaid supplemental data addition to at least a portion of the receivedparticular image data facilitating module configured to add supplementaldata to at least a portion of the received particular image data togenerate transmission image data comprises: an advertisement dataaddition to at least a portion of the received particular image data togenerate transmission image data facilitating module.
 423. The device ofclaim 422, wherein said advertisement data addition to at least aportion of the received particular image data to generate transmissionimage data facilitating module comprises: a context-based advertisementdata addition to at least a portion of the received particular imagedata to generate transmission image data facilitating module configuredto add context-based advertisement data that is at least partially basedon the received particular image data to at least the portion of thereceived particular image data.
 424. The device of claim 423, whereinsaid context-based advertisement data addition to at least a portion ofthe received particular image data to generate transmission image datafacilitating module configured to add context-based advertisement datathat is at least partially based on the received particular image datato at least the portion of the received particular image data comprises:a context-based advertisement data addition to at least a portion of thereceived particular image data to generate transmission image datafacilitating module configured to add an animal rights donation fundadvertisement data that is at least partially based on the receivedparticular image data of a tiger at a jungle oasis, to the receivedparticular image data of the tiger at the jungle oasis.
 425. The deviceof claim 421, wherein said supplemental data addition to at least aportion of the received particular image data facilitating moduleconfigured to add supplemental data to at least a portion of thereceived particular image data to generate transmission image datacomprises: a related visual data addition to at least a portion of thereceived particular image data to generate transmission image datafacilitating module configured to add related visual data related to thereceived particular image data to at least a portion of the receivedparticular image data to generate transmission image data. 426.(canceled)
 427. The device of claim 327, wherein said receivedparticular image data transmitting to at least one requestor modulecomprises: a portion of received particular image data modification togenerate transmission image data facilitating module configured tomodify data of a portion of the received particular image data togenerate transmission image data; and a generated transmission imagedata transmitting to at least one requestor module configured totransmit at the generated transmission image data to at least onerequestor.
 428. (canceled)
 429. (canceled)
 430. (canceled) 431.(canceled)
 432. (canceled)
 433. (canceled)
 434. The device of claim 327,wherein said received particular image data transmitting to at least onerequestor module comprises: a lower-resolution version of receivedparticular image data transmitting to at least one requestor moduleconfigured to transmit a lower-resolution version of the receivedparticular image data to the at least one requestor; and afull-resolution version of received particular image data transmittingto at least one requestor module configured to transmit afull-resolution version of the received particular image data to the atleast one requestor.
 435. (canceled)
 436. (canceled)
 437. (canceled)438. (canceled)